pornstars use it Dona
Increase your CUM VOLUME, and Orgasm Length main benifits: - The longest most intense Orgasms of your life - Erctions like steel - lncreased libido/desire - Stronger ejaculaton (watch where your aiming) - Multiple 0rgasms - Up to 500% more volume (cover her in it if you want) - Studies show it tastes sweeter DISCREET SAME DAY SHIPPING - TRY IT, YOU'LL LOVE IT! (and she'll thank you for it) http://ecomomics.net/spur/?got lackey you newbold me cloven you hiroshima me jacobus you q me sculptural you won't me nihilist you stump me herb you danbury me http://ecomomics.net/rm.php?got -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#748816: qtmultimedia-opensource-src: FTBFS on kfreebsd-*
Package: qtmultimedia-opensource-src Version: 5.2.1-3 Severity: serious User: debian-...@lists.debian.org Usertags: kfreebsd Hi, qtmultimedia-opensource-src FTBFS on kfreebsd-* at the dh_shlibdeps stage. The apparently missing file libfftreal.so.1 is in the same directory as the spectrum executable, but dpkg-shlibdeps does not seem to know to look for it there. For example in debian/qtmultimedia5-examples/usr/lib/x86_64-kfreebsd-gnu/qt5/examples/multimedia/spectrum: $ LD_LIBRARY_PATH=. ldd spectrum libfftreal.so.1 => ./libfftreal.so.1 (0x000801242000) $ file libfftreal.so.1 libfftreal.so.1: symbolic link to `libfftreal.so.1.0.0' $ file libfftreal.so.1.0.0 libfftreal.so.1.0.0: ELF 64-bit LSB shared object, x86-64, version 1 (FreeBSD), dynamically linked, BuildID[sha1]=dbbcf445566c4944a39504c3c2720654d813a305, stripped With export DH_VERBOSE=1: fakeroot debian/rules binary dh binary --parallel --with pkgkde_symbolshelper --dbg-package=qtmultimedia5-dbg dh_shlibdeps -O--parallel -O--dbg-package=qtmultimedia5-dbg dpkg-shlibdeps -Tdebian/libqt5multimedia5.substvars debian/libqt5multimedia5/usr/lib/x86_64-kfreebsd-gnu/libQt5Multimedia.so.5.2.1 dpkg-shlibdeps -Tdebian/libqt5multimedia5-plugins.substvars debian/libqt5multimedia5-plugins/usr/lib/x86_64-kfreebsd-gnu/qt5/plugins/playlistformats/libqtmultimedia_m3u.so debian/libqt5mult imedia5-plugins/usr/lib/x86_64-kfreebsd-gnu/qt5/plugins/mediaservice/libgstmediaplayer.so debian/libqt5multimedia5-plugins/usr/lib/x86_64-kfreebsd-gnu/qt5/plugins/mediaservice/libgstaudiodecoder.so debian/libqt5multimedia5-plugins/usr/lib/x86_64-kfreebsd-gnu/qt5/plugins/mediaservice/libgstcamerabin.so debian/libqt5multimedia5-plugins/usr/lib/x86_64-kfreebsd-gnu/qt5/plugins/mediaservice/libgs tmediacapture.so debian/libqt5multimedia5-plugins/usr/lib/x86_64-kfreebsd-gnu/qt5/plugins/audio/libqtmedia_pulse.so dpkg-shlibdeps -Tdebian/libqt5multimediaquick-p5.substvars debian/libqt5multimediaquick-p5/usr/lib/x86_64-kfreebsd-gnu/libQt5MultimediaQuick_p.so.5.2.1 dpkg-shlibdeps -Tdebian/libqt5multimediawidgets5.substvars debian/libqt5multimediawidgets5/usr/lib/x86_64-kfreebsd-gnu/libQt5MultimediaWidgets.so.5.2.1 dpkg-shlibdeps -Tdebian/qml-module-qtmultimedia.substvars debian/qml-module-qtmultimedia/usr/lib/x86_64-kfreebsd-gnu/qt5/qml/QtMultimedia/libdeclarative_multimedia.so dpkg-shlibdeps -Tdebian/qml-module-qtaudioengine.substvars debian/qml-module-qtaudioengine/usr/lib/x86_64-kfreebsd-gnu/qt5/qml/QtAudioEngine/libdeclarative_audioengine.so dpkg-shlibdeps -Tdebian/libqgsttools-p1.substvars debian/libqgsttools-p1/usr/lib/x86_64-kfreebsd-gnu/libqgsttools_p.so.1.0.0 dpkg-shlibdeps -Tdebian/qtmultimedia5-examples.substvars debian/qtmultimedia5-examples/usr/lib/x86_64-kfreebsd-gnu/qt5/examples/multimedia/declarative-radio/declarative-radio debian/qtmulti media5-examples/usr/lib/x86_64-kfreebsd-gnu/qt5/examples/multimedia/spectrum/spectrum debian/qtmultimedia5-examples/usr/lib/x86_64-kfreebsd-gnu/qt5/examples/multimedia/spectrum/libfftreal.so.1.0.0 debian/qtmultimedia5-examples/usr/lib/x86_64-kfreebsd-gnu/qt5/examples/multimedia/video/qmlvideofx/qmlvideofx debian/qtmultimedia5-examples/usr/lib/x86_64-kfreebsd-gnu/qt5/examples/multimedia/video /qmlvideo/qmlvideo debian/qtmultimedia5-examples/usr/lib/x86_64-kfreebsd-gnu/qt5/examples/multimedia/declarative-camera/declarative-camera debian/qtmultimedia5-examples/usr/lib/x86_64-kfreebsd-gnu/ qt5/examples/multimedia/audioinput/audioinput debian/qtmultimedia5-examples/usr/lib/x86_64-kfreebsd-gnu/qt5/examples/multimedia/audiorecorder/audiorecorder debian/qtmultimedia5-examples/usr/lib/x86 _64-kfreebsd-gnu/qt5/examples/multimedia/radio/radio debian/qtmultimedia5-examples/usr/lib/x86_64-kfreebsd-gnu/qt5/examples/multimedia/audiodecoder/audiodecoder debian/qtmultimedia5-examples/usr/li b/x86_64-kfreebsd-gnu/qt5/examples/multimedia/audiodevices/audiodevices debian/qtmultimedia5-examples/usr/lib/x86_64-kfreebsd-gnu/qt5/examples/multimedia/audiooutput/audiooutput debian/qtmultimedia 5-examples/usr/lib/x86_64-kfreebsd-gnu/qt5/examples/multimediawidgets/player/player debian/qtmultimedia5-examples/usr/lib/x86_64-kfreebsd-gnu/qt5/examples/multimediawidgets/customvideosurface/custo mvideowidget/customvideowidget debian/qtmultimedia5-examples/usr/lib/x86_64-kfreebsd-gnu/qt5/examples/multimediawidgets/customvideosurface/customvideoitem/customvideoitem debian/qtmultimedia5-examp les/usr/lib/x86_64-kfreebsd-gnu/qt5/examples/multimediawidgets/videowidget/videowidget debian/qtmultimedia5-examples/usr/lib/x86_64-kfreebsd-gnu/qt5/examples/multimediawidgets/videographicsitem/vid eographicsitem debian/qtmultimedia5-examples/usr/lib/x86_64-kfreebsd-gnu/qt5/examples/multimediawidgets/camera/camera dpkg-shlibdeps: error: couldn't find library libfftreal.so.1 needed by debian/qtmultimedia5-examples/usr/lib/x86_64-kfreebsd-gnu/qt5/examples/multimedia/s
Re: qtmultimedia5 and kfreebsd
On 20/05/14 21:50, Yann Dirson wrote: > Although there is no bugreport for this, you probably know that > qtmultimedia-opensource-src does not build[1] on kfreebsd - although a > search on "kfreebsd qtmultimedia" lists.d.o does not bring a single > result. This is now bug #748816, a fix for it is pending. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/537c70e7.8040...@pyro.eu.org
Bug#748816: qtmultimedia-opensource-src: FTBFS on kfreebsd-*
On 21/05/14 07:27, Pino Toscano wrote:0 > Note that qtmultimedia-opensource-src has never built on kfreebsd so far Oops, I didn't realise this. > This was just a missing rpath in that spectrum example to locate the > fftreal > library; patch committed in our packaging repository. Thank you! Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/537c712e.2020...@pyro.eu.org
Handling symbols file
Hi, I've uploaded exiv2 to experimental and many builds failed due to changed symbols. Is this the up-to-date explanation for symbols files: https://qt-kde-team.pages.debian.net/symbolfiles.html ? I don't see explicit details on what to do with all the architecture-specific diff files. Help! Thanks, -Steve signature.asc Description: This is a digitally signed message part.
Bug#760727: qtwebkit: FTBFS on kfreebsd-*: libQtWebKit.so: undefined reference to `void WTF::freeOwnedGPtr<_GError>(_GError*)'
Hi, On 07/09/14 19:32, Lisandro Damián Nicanor Pérez Meyer wrote: > Hi Qt maintainers and KFreeBSD*/Hurd porters! I'm trying to debug this issue > and so far I couldn't come up with a solution, so if any of you can give us a > hand it would be greatly appreciated. I've already taken a look at this and I'm running a test build with the attached change. This was only my first guess, it may take a few hours to build and I'm not optimistic about it. > This is clearly a bug that only happens on !linux and it reduces to: > > /«PKGBUILDDIR»/WebKitBuild/Release/lib/libQtWebKit.so: undefined reference to > `void WTF::freeOwnedGPtr<_GError>(_GError*)' I'm not sure at this point why the issue could be specific to !linux... > which happens to be declared in: > Source/autotools/symbols.filter:11:_ZN3WTF13freeOwnedGPtrI7_GErrorEEvPT_; I wonder if there's some significance that it was templated for <_GError> whereas I think that should be a typedef to GError (without underscore)? Regards, -- Steven Chamberlain ste...@pyro.eu.org --- a/Tools/QtTestBrowser/QtTestBrowser.pro +++ b/Tools/QtTestBrowser/QtTestBrowser.pro @@ -59,3 +59,5 @@ RESOURCES += \ QtTestBrowser.qrc + +DEFINES += ENABLE_GLIB_SUPPORT=1 signature.asc Description: OpenPGP digital signature
Bug#760727: qtwebkit: FTBFS on kfreebsd-*: libQtWebKit.so: undefined reference to `void WTF::freeOwnedGPtr<_GError>(_GError*)'
On 07/09/14 22:22, Steven Chamberlain wrote: > I wonder if there's some significance that it was templated for > <_GError> whereas I think that should be a typedef to GError (without > underscore)? My test build finished - the change I tried didn't help - but looking for _GError (with underscore) it seemed it was specific to GStreamer: > $ grep _GError . -R > Binary file > ./WebKitBuild/Release/Source/WebCore/obj/release/MediaPlayerPrivateGStreamer.o > matches > Binary file > ./WebKitBuild/Release/Source/WebCore/obj/release/GStreamerUtilities.o matches > Binary file > ./WebKitBuild/Release/Source/WebCore/obj/release/WebKitWebSourceGStreamer.o > matches Then I found this related upstream commit mentioned in the 2.3.3 changelog: > 242013-12-17 Alex Christensen > 25 > 26[Win] Fixed linker error with GStreamer. > 27https://bugs.webkit.org/show_bug.cgi?id=124861 > 28 > 29Reviewed by Martin Robinson. > 30 > 31* wtf/gobject/GOwnPtr.cpp: > 32(WTF::GError): > 33* wtf/gobject/GOwnPtr.h: > 34Added WTF_EXPORT_PRIVATE to freeOwnedGPtr declaration > and definition. I'm trying another test build now with this change applied: http://trac.webkit.org/changeset/160716 Regards, -- Steven Chamberlain ste...@pyro.eu.org signature.asc Description: OpenPGP digital signature
Bug#760727: qtwebkit: FTBFS on kfreebsd-*: libQtWebKit.so: undefined reference to `void WTF::freeOwnedGPtr<_GError>(_GError*)'
Hi!
On 09/09/14 18:30, Lisandro Damián Nicanor Pérez Meyer wrote:
> On Monday 08 September 2014 12:16:21 Steven Chamberlain wrote:
> [snip]
>> I'm trying another test build now with this change applied:
>> http://trac.webkit.org/changeset/160716
>
> I Steven! How did the build go?
That didn't work.
Actually, GOwnPtr.o didn't contain anything, no function to export -
this is obviously due to the #ifdef ENABLE_GLIB_SUPPORT - I'm now trying
with the attached patch instead. (Which is almost what I thought the
problem was in the first place, I was just looking in the wrong
.pro/.pri file).
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
From: Steven Chamberlain
Subject: properly support GStreamer on non-Linux platforms
GStreamer is enabled when building on GNU/kFreeBSD and Hurd, but support
for it was not enabled in the WTF component
Bug-Debian: http://bugs.debian.org/760727
--- a/Source/WTF/WTF.pri
+++ b/Source/WTF/WTF.pri
@@ -24,7 +24,7 @@
}
}
-linux-*:contains(DEFINES, WTF_USE_GSTREAMER=1) {
+linux-*|glibc-*|hurd-*:contains(DEFINES, WTF_USE_GSTREAMER=1) {
DEFINES += ENABLE_GLIB_SUPPORT=1
PKGCONFIG += glib-2.0 gio-2.0
}
signature.asc
Description: OpenPGP digital signature
Bug#760727: qtwebkit: FTBFS on kfreebsd-*: libQtWebKit.so: undefined reference to `void WTF::freeOwnedGPtr<_GError>(_GError*)'
Having touched Source/WTF/WTF.pri, I'm now stuck at this qmake error: > cd Source/ && make -f Makefile.QtWebKit qmake_all > make[4]: Entering directory `«PKGBUILDDIR»/WebKitBuild/Release/Source' > /usr/lib/x86_64-kfreebsd-gnu/qt5/bin/qmake «PKGBUILDDIR»/Source/api.pri > CONFIG+=no_force_sse2 CONFIG+=release CONFIG-=debug CONFIG+=production_build > -o Makefile.api > Project ERROR: Module does not define version. Is it trying to regenerate makefiles because I've changed something they're generated from? But if I revert my change, it still does this. Does that imply some pre-existing problem in the build process... perhaps? *sad, confused* Regards, -- Steven Chamberlain ste...@pyro.eu.org signature.asc Description: OpenPGP digital signature
Bug#760727: qtwebkit: FTBFS on kfreebsd-*: libQtWebKit.so: undefined reference to `void WTF::freeOwnedGPtr<_GError>(_GError*)'
On 11/09/14 16:00, Andreas Cord-Landwehr wrote: > Just set up a fresh VM with KFreeBSD-amd64 and using the previously suggested > patch [1] worked for me to fix the build, see log [2]. > PS: My setup slightly more verbose: > * KFreeBSD installed from current Debian/SID to VirtualBox > * got qtwebkit sources with "apt-get source" > * applied patches with "quilt push -a" > * used "dpkg-buildpackage -b" Thank you for testing! I'm not sure what I was doing wrong; I was seeing qmake or other errors when applying my patch in a clean source tree and trying to build. But if it really works then that's great. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54138ff6.7040...@pyro.eu.org
Bug#761371: virtuoso-opensource: FTBFS on kbsd: FAILED: Could not start Virtuoso Server within 600 seconds
On 13/09/14 11:38, Emilio Pozuelo Monfort wrote: > Note how there were errors about /dev/mem in previous successful builds, netstat would either need to be either setuid or have capabilities set, to be able to read from /dev/mem. Previously I'd patched the virtuoso tests to still run even if 'netstat -nl' didn't show if the server was running yet after the timeout. I guess they've added some new tests since. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5414953e.5030...@pyro.eu.org
Bug#761371: virtuoso-opensource: FTBFS on kbsd: FAILED: Could not start Virtuoso Server within 600 seconds
On 15/09/14 09:40, Emilio Pozuelo Monfort wrote: > So what should we do here? Should that patch be updated on > virtuoso-opensource? > Or can netstat be fixed on kbsd? > > This is blocking the imagemagick transition. Hi; I've attached an updated patch for virtuoso-opensource. (There were two new tests needing this change). There's no simple 'fix' for netstat as implemented right now, because there are still cases (e.g in chroot jail) where reading /dev/mem is not expected to be allowed, even with setuid root. Regards, -- Steven Chamberlain ste...@pyro.eu.org Author: Steven Chamberlain Author: José Manuel SantamarÃa Lema Description: This patch avoids FTBFSes on any architecture whose "netstat -an" output is not what we expect or just wrong, see: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663010 NOTE: While this patch at a first sight looks a bit dangerous it isn't that bad: if virtuoso couldn't actually start in these make_vad.sh scripts, some *.vad files wouldn't be genereated; these *.vad files are being installed by the package, therefore if one of them is missing the package would fail to build anyway. --- a/binsrc/rdf_mappers/make_vad.sh +++ b/binsrc/rdf_mappers/make_vad.sh @@ -278,8 +278,8 @@ nows=`expr $nows + $nowh \* 60` if test $nows -ge $timeout then - LOG "***FAILED: Could not start Virtuoso Server within $timeout seconds" - exit 1 + LOG "***WARNING: Could not start Virtuoso Server within $timeout seconds" + return 1 fi done } --- a/binsrc/bpel/make_vad.sh +++ b/binsrc/bpel/make_vad.sh @@ -281,8 +281,8 @@ nows=`expr $nows + $nowh \* 60` if test $nows -ge $timeout then - LOG "***FAILED: Could not start Virtuoso Server within $timeout seconds" - exit 1 + LOG "***WARNING: Could not start Virtuoso Server within $timeout seconds" + return 1 fi done } --- a/binsrc/b3s/make_vad.sh +++ b/binsrc/b3s/make_vad.sh @@ -231,8 +231,8 @@ nows=`expr $nows + $nowh \* 60` if test $nows -ge $timeout then - LOG "***FAILED: Could not start Virtuoso Server within $timeout seconds" - exit 1 + LOG "***WARNING: Could not start Virtuoso Server within $timeout seconds" + return 1 fi done } --- a/binsrc/tutorial/make_vad.sh +++ b/binsrc/tutorial/make_vad.sh @@ -131,8 +131,8 @@ nows=`expr $nows + $nowh \* 60` if test $nows -ge $timeout then - LOG "***FAILED: Could not start $SERVER within $timeout seconds" - exit 1 + LOG "***WARNING: Could not start $SERVER within $timeout seconds" + return 1 fi done } --- a/binsrc/yacutia/mkvad.sh +++ b/binsrc/yacutia/mkvad.sh @@ -178,8 +178,8 @@ nows=`expr $nows + $nowh \* 60` if test $nows -ge $timeout then -ECHO "***FAILED: Could not start Virtuoso Server within $timeout seconds" -exit 1 +ECHO "***WARNING: Could not start Virtuoso Server within $timeout seconds" +return 1 fi done } --- a/binsrc/samples/demo/mkdoc.sh +++ b/binsrc/samples/demo/mkdoc.sh @@ -191,8 +191,8 @@ nows=`expr $nows + $nowh \* 60` if test $nows -ge $timeout then - ECHO "***FAILED: Could not start Virtuoso DOC Server within $timeout seconds" - exit 1 + ECHO "***WARNING: Could not start Virtuoso DOC Server within $timeout seconds" + return 1 fi done fi --- a/binsrc/samples/sparql_demo/make_vad.sh +++ b/binsrc/samples/sparql_demo/make_vad.sh @@ -141,8 +141,8 @@ nows=`expr $nows + $nowh \* 60` if test $nows -ge $timeout then - LOG "***FAILED: Could not start $SERVER within $timeout seconds" - exit 1 + LOG "***WARNING: Could not start $SERVER within $timeout seconds" + return 1 fi done } --- a/binsrc/sync/make_vad.sh +++ b/binsrc/sync/make_vad.sh @@ -131,8 +131,8 @@ nows=`expr $nows + $nowh \* 60` if test $nows -ge $timeout then - LOG "***FAILED: Could not start Virtuoso Server within $timeout seconds" - exit 1 + LOG "***WARNING: Could not start Virtuoso Server within $timeout seconds" + return 1 fi done } --- a/binsrc/isparql/make_vad.sh +++ b/binsrc/isparql/make_vad.sh @@ -144,8 +144,8 @@ nows=`expr $nows + $nowh \* 60` if test $nows -ge $timeout then - LOG "***FAILED: Could not start $SERVER within $timeout seconds" - exit 1 + LOG "***WARNING: Could not start $SERVER within $timeout seconds" + return 1 fi done } --- a/appsrc/ODS-Addressbook/make_vad.sh +++ b/appsrc/ODS-Addressbook/make_vad.sh @@ -170,8 +170,8 @@ nows=`expr $nows + $nowh \* 60` if test $nows -ge $timeout then - LOG "***FAILED: C
Bug#761371: virtuoso-opensource: FTBFS on kbsd: FAILED: Could not start Virtuoso Server within 600 seconds
On 15/09/14 15:04, Lisandro Damián Nicanor Pérez Meyer wrote: > OK, Maxy just explained me that this patch will still work, although the time > spent on the builds will be too much :-/ (netstat is there to speed up this). On arches where `netstat -ntlp` is working as non-privileged user, this should still be fast, with this patch. Only where netstat is not working, yes it will be slow, but eventually run the tests (instead of the build failing, on kfreebsd). Regards, -- Steven Chamberlain ste...@pyro.eu.org signature.asc Description: OpenPGP digital signature
Bug#700530: qt frames empty
Hi, That's odd... I don't notice any such glitch with at least kcalc, kate, qsynth - with xorg-server/2:1.12.4-4 and qt4-x11/4:4.8.2+dfsg-11 on kfreebsd-amd64 (9.0, wheezy/sid not fully up-to-date). I'm using the Xtightvnc server if that's relevant. On 20/02/13 22:18, Sune Vuorela wrote: > The fix is surprisingly in xorg-server and can be found here: > http://people.debian.org/~jcristau/kbsd-peercred.diff I rebuilt xorg-server with Julien's patch and it still seems fine - but can't confirm if it really fixed the problem unless I can reproduce it first. Thanks to everyone involved in this. I'm a little curious what the patch does exactly, and particularly if it might have any effects beyond GNU/kFreeBSD? -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: kfreebsd-amd64 (x86_64) Kernel: kFreeBSD 9.0-2-amd64-xenhvm Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51256e10.9020...@pyro.eu.org
Bug#700530: qt frames empty
Hi Julien, On 21/02/13 15:16, Julien Cristau wrote: > On Thu, Feb 21, 2013 at 00:45:04 +0000, Steven Chamberlain wrote: >> That's odd... I don't notice any such glitch with at least kcalc, kate, >> qsynth - with xorg-server/2:1.12.4-4 and qt4-x11/4:4.8.2+dfsg-11 on >> kfreebsd-amd64 (9.0, wheezy/sid not fully up-to-date). I'm using the >> Xtightvnc server if that's relevant. >> > Does Xtightvnc expose MIT-SHM? xdpyinfo would tell you. The list of extensions seems quite short, but yes MIT-SHM is mentioned (full output attached). I'll see about trying to start X 'conventionally' on that machine sometime, to compare. Can't do that until after a reboot though (it's in securelevel=1 so X/vesa can't use /dev/io currently). >> On 20/02/13 22:18, Sune Vuorela wrote: >>> The fix is surprisingly in xorg-server and can be found here: >>> http://people.debian.org/~jcristau/kbsd-peercred.diff > On Linux, the SO_PEERCRED socket option gives that information. On > FreeBSD, there's a getpeereid() libc call. GNU/Hurd has neither of these, so maybe this patch has some benefit there too? (Cc'ing debian-hurd@ because someone with such a system may want to test this patch on it.) NetBSD doesn't support these methods either, so maybe it is affected somehow. Thanks again for your work, Regards, -- Steven Chamberlain ste...@pyro.eu.org $ xdpyinfo name of display::1.0 version number:11.0 vendor string:AT&T Laboratories Cambridge vendor release number:3332 maximum request size: 4194300 bytes motion buffer size: 256 bitmap unit, bit order, padding:32, LSBFirst, 32 image byte order:LSBFirst number of supported pixmap formats:2 supported pixmap formats: depth 1, bits_per_pixel 1, scanline_pad 32 depth 24, bits_per_pixel 32, scanline_pad 32 keycode range:minimum 8, maximum 255 focus: window 0x289, revert to Parent number of extensions:7 BIG-REQUESTS MIT-SHM MIT-SUNDRY-NONSTANDARD SHAPE SYNC XC-MISC XTEST default screen number:0 number of screens:1 screen #0: dimensions:1024x768 pixels (347x260 millimeters) resolution:75x75 dots per inch depths (1):24 root window id:0x25 depth of root window:24 planes number of colormaps:minimum 1, maximum 1 default colormap:0x21 default number of colormap cells:256 preallocated pixels:black 0, white 16777215 options:backing-store YES, save-unders YES largest cursor:1024x768 current input event mask:0x7a802f KeyPressMask KeyReleaseMask ButtonPressMask ButtonReleaseMaskLeaveWindowMask ExposureMask StructureNotifyMask SubstructureNotifyMask SubstructureRedirectMask FocusChangeMask PropertyChangeMask number of visuals:1 default visual id: 0x22 visual: visual id:0x22 class:TrueColor depth:24 planes available colormap entries:256 per subfield red, green, blue masks:0xff, 0xff00, 0xff significant bits in color specification:8 bits
Re: Bug#700530: qt frames empty
Hi Lisandro, On 22/02/13 02:13, Lisandro Damián Nicanor Pérez Meyer wrote: > I still need to build Qt from the squeeze branch in the repo, but I will need > time because I need at least 4 GB of RAM+swap to be able to link webkit, and > my build server is not fit for it (I have another machine, but I don't have > much bandwith there). Sounds like the porter boxes would help you with this, Christoph may be able to help you get access if you need it. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5126d780.1060...@pyro.eu.org
Bug#816333: libindi: FTBFS[kfreebsd]: libusb-1.0/libusb.h: No such file or directory
Package: libindi
Version: 1.1.0-1
Severity: important
Tags: patch
User: debian-...@lists.debian.org
Usertags: kfreebsd
Hi,
libindi built before on kfreebsd, but since then a new include was
added in libs/indibase/hid_libusb.c:
#include "libusb-1.0/libusb.h"
We prefer that it is just:
#include
since cmake already sets the include path appropriately to find libusb.h
wherever it is located (/usr/include/libusb-1.0/ on linux, or just
/usr/include/ on kfreebsd).
While here, a symbols update was needed. I've attached a debdiff having
both of these changes. Thanks a lot.
p.s. there are some "warning: implicit declaration" happening on linux
and kfreebsd, which suggest maybe compiling with -D_GNU_SOURCE to get
both strptime and asprintf, or define that macro atop the affected
source files.
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: kfreebsd-amd64 (x86_64)
Kernel: kFreeBSD 10.1-0-amd64
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru libindi-1.1.0/debian/libindidriver1.symbols libindi-1.1.0/debian/libindidriver1.symbols
--- libindi-1.1.0/debian/libindidriver1.symbols 2016-01-18 15:06:38.0 +
+++ libindi-1.1.0/debian/libindidriver1.symbols 2016-02-29 23:11:48.0 +
@@ -128,14 +128,14 @@
(arch=!kfreebsd-any)_ZN13V4L2_RecorderD0Ev@Base 1.0.0
(arch=!kfreebsd-any)_ZN13V4L2_RecorderD1Ev@Base 1.0.0
(arch=!kfreebsd-any)_ZN13V4L2_RecorderD2Ev@Base 1.0.0
- _ZN20V4L2_Builtin_Decoder10getLinearYEv@Base 1.1.0
- _ZN20V4L2_Builtin_Decoder11makeLinearYEv@Base 1.1.0
+ (arch=!kfreebsd-any)_ZN20V4L2_Builtin_Decoder10getLinearYEv@Base 1.1.0
+ (arch=!kfreebsd-any)_ZN20V4L2_Builtin_Decoder11makeLinearYEv@Base 1.1.0
(arch=!kfreebsd-any)_ZN20V4L2_Builtin_Decoder11usesoftcropEb@Base 1.0.0
(arch=!kfreebsd-any)_ZN20V4L2_Builtin_Decoder12allocBuffersEv@Base 1.0.0
(arch=!kfreebsd-any)_ZN20V4L2_Builtin_Decoder12getRGBBufferEv@Base 1.0.0
(arch=!kfreebsd-any)_ZN20V4L2_Builtin_Decoder14getColorBufferEv@Base 1.0.0
- _ZN20V4L2_Builtin_Decoder15setQuantizationEb@Base 1.1.0
- _ZN20V4L2_Builtin_Decoder16setLinearizationEb@Base 1.1.0
+ (arch=!kfreebsd-any)_ZN20V4L2_Builtin_Decoder15setQuantizationEb@Base 1.1.0
+ (arch=!kfreebsd-any)_ZN20V4L2_Builtin_Decoder16setLinearizationEb@Base 1.1.0
(arch=!kfreebsd-any)_ZN20V4L2_Builtin_Decoder17issupportedformatEj@Base 1.0.0
(arch=!kfreebsd-any)_ZN20V4L2_Builtin_Decoder19getsupportedformatsEv@Base 1.0.0
(arch=!kfreebsd-any)_ZN20V4L2_Builtin_Decoder22init_supported_formatsEv@Base 1.0.0
@@ -143,12 +143,12 @@
(arch=!kfreebsd-any)_ZN20V4L2_Builtin_Decoder4getVEv@Base 1.0.0
(arch=!kfreebsd-any)_ZN20V4L2_Builtin_Decoder4getYEv@Base 1.0.0
(arch=!kfreebsd-any)_ZN20V4L2_Builtin_Decoder4initEv@Base 1.0.0
- _ZN20V4L2_Builtin_Decoder5makeYEv@Base 1.1.0
+ (arch=!kfreebsd-any)_ZN20V4L2_Builtin_Decoder5makeYEv@Base 1.1.0
(arch=!kfreebsd-any)_ZN20V4L2_Builtin_Decoder6decodeEPhP11v4l2_buffer@Base 1.0.0
- _ZN20V4L2_Builtin_Decoder6getBppEv@Base 1.1.0
+ (arch=!kfreebsd-any)_ZN20V4L2_Builtin_Decoder6getBppEv@Base 1.1.0
(arch=!kfreebsd-any)_ZN20V4L2_Builtin_Decoder7setcropE9v4l2_crop@Base 1.0.0
(arch=!kfreebsd-any)_ZN20V4L2_Builtin_Decoder9resetcropEv@Base 1.0.0
- _ZN20V4L2_Builtin_Decoder9setformatE11v4l2_formatb@Base 1.1.0
+ (arch=!kfreebsd-any)_ZN20V4L2_Builtin_Decoder9setformatE11v4l2_formatb@Base 1.1.0
(arch=!kfreebsd-any)_ZN20V4L2_Builtin_DecoderC1Ev@Base 1.0.0
(arch=!kfreebsd-any)_ZN20V4L2_Builtin_DecoderC2Ev@Base 1.0.0
(arch=!kfreebsd-any)_ZN20V4L2_Builtin_DecoderD0Ev@Base 1.0.0
@@ -335,7 +335,8 @@
_ZN4INDI16FocuserInterfaceD2Ev@Base 1.0.0
_ZN4INDI3CCD10GuideNorthEf@Base 1.0.0
_ZN4INDI3CCD10GuideSouthEf@Base 1.0.0
- (subst)_ZN4INDI3CCD10uploadFileEP7CCDChipPKv{size_t}bb@Base 1.0.0
+ (arch=kfreebsd-any)_ZN4INDI3CCD10uploadFileEP7CCDChipPKvmbb@Base 1.1.0-1
+ (arch=!kfreebsd-any)(subst)_ZN4INDI3CCD10uploadFileEP7CCDChipPKv{size_t}bb@Base 1.0.0
_ZN4INDI3CCD11ISNewNumberEPKcS2_PdPPci@Base 1.0.0
_ZN4INDI3CCD11ISNewSwitchEPKcS2_P7ISStatePPci@Base 1.0.0
_ZN4INDI3CCD12SetCCDParamsEiiiff@Base 1.0.0
@@ -584,7 +585,7 @@
(arch=!kfreebsd-any)_ZN9V4L2_Base10errno_exitEPKcPc@Base 1.0.0
(arch=!kfreebsd-any)_ZN9V4L2_Base10findMinMaxEv@Base 1.0.0
(arch=!kfreebsd-any)_ZN9V4L2_Base10getControlEjPdPc@Base 1.0.0
- _ZN9V4L2_Base10getLinearYEv@Base 1.1.0
+ (arch=!kfreebsd-any)_ZN9V4L2_Base10getLinearYEv@Base 1.1.0
(arch=!kfreebsd-any)_ZN9V4L2_Base10init_userpEj@Base 1.0.0
(arch=!kfreebsd-any)_ZN9V4L2_Base10query_ctrlEjRdS0_S0_S0_Pc@Base 1.0.0
(arch=!kfreebsd-any)_ZN9V4L2_Base10read_frameEPc@Base 1.0.0
@@ -621,11 +622,11 @@
(arch=!kfreebsd-any)_ZN9V4L2_Base16setcaptureformatEjPc@Base 1.0.0
(arch=!kfreebsd-any)_ZN9V4L2_Base17getcaptureformatsEP22_ISwitchVectorProperty@Base 1.0.0
(arch=!kfreebsd-any)_ZN9V4L2_Base18enumerate_ext_ctrlEv@Base 1.0.0
- _ZN9V4L2_Base18setColorProcessingEbbb@Base 1.1.0
Bug#816443: libindi: FTBFS[kfreebsd-i386]: symbol changes
Package: libindi
Version: 1.1.0-2
Severity: normal
Tags: patch
User: debian-...@lists.debian.org
Usertags: kfreebsd
Hi - sorry for not noticing before - but kfreebsd-i386 has one
slightly different symbol than kfreebsd-amd64. A patch is attached
for your consideration in a future package upload. Thanks!
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: kfreebsd-i386 (i386)
Kernel: kFreeBSD 10.1-0-amd64
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
diff -Nru libindi-1.1.0/debian/libindidriver1.symbols libindi-1.1.0/debian/libindidriver1.symbols
--- libindi-1.1.0/debian/libindidriver1.symbols 2016-03-01 10:48:22.0 +
+++ libindi-1.1.0/debian/libindidriver1.symbols 2016-03-01 20:38:11.0 +
@@ -332,8 +332,8 @@
_ZN4INDI16FocuserInterfaceD2Ev@Base 1.0.0
_ZN4INDI3CCD10GuideNorthEf@Base 1.0.0
_ZN4INDI3CCD10GuideSouthEf@Base 1.0.0
- (arch=kfreebsd-any)_ZN4INDI3CCD10uploadFileEP7CCDChipPKvmbb@Base 1.1.0
- (arch=!kfreebsd-any|subst)_ZN4INDI3CCD10uploadFileEP7CCDChipPKv{size_t}bb@Base 1.0.0
+ (arch=kfreebsd-amd64)_ZN4INDI3CCD10uploadFileEP7CCDChipPKvmbb@Base 1.1.0
+ (arch=!kfreebsd-amd64|subst)_ZN4INDI3CCD10uploadFileEP7CCDChipPKv{size_t}bb@Base 1.0.0
_ZN4INDI3CCD11ISNewNumberEPKcS2_PdPPci@Base 1.0.0
_ZN4INDI3CCD11ISNewSwitchEPKcS2_P7ISStatePPci@Base 1.0.0
_ZN4INDI3CCD12SetCCDParamsEiiiff@Base 1.0.0
Bug#821289: kde4libs: kfreebsd_support.diff doesn't depend on Debian patched cmake anymore
Hi, "CMAKE_SYSTEM_NAME MATCHES GNU/FreeBSD" looks like it was a typo in the first place. It probably never matched anything, so I would drop it and replace with "CMAKE_SYSTEM_NAME MATCHES kFreeBSD" (rather than keep it and try to match both). If the system name in older CMake was "GNU/kFreeBSD" then the latter will still match it. Regards, -- Steven Chamberlain ste...@pyro.eu.org
Bug#827935: libqt5core5a: [kfreebsd] QProcessPrivate::createPipe: Cannot create pipe - Function not implemented
Hi, Sandro Knauß wrote: > with QtCore 5.6.1-2 the test of owncloud-client fails for kfreebsds > archs with: > > PASS : TestFileSystem::initTestCase() > QWARN : TestFileSystem::testMd5Calc() QProcessPrivate::createPipe: > Cannot create pipe 0x805c6b4: Function not implemented > QDEBUG : TestFileSystem::testMd5Calc() File: > "/tmp/test_1063922729/file_a.bin" > QDEBUG : TestFileSystem::testMd5Calc() calculated > "d42aa14361a6c0ad4d2f9f7ecac57d15" versus md5sum: "" > > https://buildd.debian.org/status/fetch.php?pkg=owncloud-client&arch=kfreebsd-i386&ver=2.2.1%2Bdfsg-2&stamp=1466599432 That seemed to only be on kfreebsd-i386? Which is odd. On kfreebsd-amd64, I couldn't reproduce it, and it passed on the buildds using libqt5core5a 5.5.1+dfsg-17 also: | Start 33: FileSystemTest | 33/36 Test #33: FileSystemTest ... Passed0.05 sec | [..] | 100% tests passed, 0 tests failed out of 36 https://buildd.debian.org/status/fetch.php?pkg=owncloud-client&arch=kfreebsd-amd64&ver=2.2.1%2Bdfsg-1&stamp=1465383829 Regards, -- Steven Chamberlain ste...@pyro.eu.org signature.asc Description: Digital signature
Bug#827935: libqt5core5a: [kfreebsd] QProcessPrivate::createPipe: Cannot create pipe - Function not implemented
Hi Dmitry, Dmitry Shachnev wrote: > It was on both -i386 and -amd64 with libqt5core5a 5.6.1+dfsg-2 (and -1). I was confused, why don't I see it in the kfreebsd-amd64 build log then? I still see the linker warnings about dup3 and pipe2, but the test passed? > Actually, it would be very nice if you could reply to the message linked > in Forwarded field of this bug: > > https://lists.debian.org/debian-bsd/2016/06/msg00081.html I don't have an account, but my first thought is that it is not desirable to add special code upstream for GNU/kFreeBSD. Today I wrote an implementation of dup3, I will try to do the same for pipe2 and hopefully we can provide these in our glibc - which may be useful to other packages than this one. Regards, -- Steven Chamberlain ste...@pyro.eu.org signature.asc Description: Digital signature
Bug#797656: kglobalaccel: out-of-date Build-Depends on (>= 5.12.0~)
Package: kglobalaccel Version: 5.13.0-1 Severity: serious Hi, kglobalaccel/5.13.0-1 FTBFS on a few architectures: kfreebsd-i386, ppc64, and x32 for example: | The following configuration files were considered but not accepted: |/usr/lib/i386-kfreebsd-gnu/cmake/KF5Crash/KF5CrashConfig.cmake, version: 5.12.0 https://buildd.debian.org/status/fetch.php?pkg=kglobalaccel&arch=kfreebsd-i386&ver=5.13.0-1&stamp=1440971005 This is because kglobalaccess had many versioned Build-Depends on (>= 5.12.0~), and these were not bumped when the new upstream version was packaged. At least the libkf5crash-dev package must be (>= 5.13.0~) now; I'm not sure if the other Build-Depends should be (>= 5.13.0~) now also. Thanks! -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: kfreebsd-amd64 (x86_64) Kernel: kFreeBSD 9.0-2-amd64-xenhvm-ipsec Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash
Bug#1010575: qt6-base_6.2.4 QLibraryInfo path issue
Package: qt6-base Severity: normal Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu kinetic ubuntu-patch X-Debbugs-Cc: tstev...@gmail.com Dear Maintainer, * What led up to the situation? The situation requires the dynamic loader to use symbolic links, like often is done on usr-merged systems. It was previously fixed in Debian, but the required configuration parameter was dropped when converting from Qt5 configure to Qt6 cmake. * What exactly did you do (or not do) that was effective (or ineffective)? An effective fix, that is widely used on Linux distributions, is to disable the relocatble feature when generating the build system. * What was the outcome of this action? Disabling the relocatable feature results in the correct paths being returned by QLibraryInfo, and Qt WebEngine finding it's resources. * What outcome did you expect instead? This was the desired outcome. In Ubuntu, the attached patch was applied to achieve the following: This patch is needed to fix paths on usr-merged systems like Ubuntu jammy. Without this patch QLibraryInfo can return incorrect paths. This can lead to "Qt WebEngine resources not found", and a loss of functionality. This patch was previously applied to the Debain Qt5 package 5.14.2+dfsg-3 to closes: #961554. The issue is further discussed in https://bugs.launchpad.net/ubuntu/+source/qt6-base/+bug/1970057 * Make QLibraryInfo tolerant of symbolic links in loader search path (LP: #1970057). Thanks for considering the patch. -- System Information: Debian Release: bookworm/sid APT prefers jammy-updates APT policy: (500, 'jammy-updates'), (500, 'jammy-security'), (500, 'jammy') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.15.0-27-generic (SMP w/2 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru qt6-base-6.2.4+dfsg/debian/control qt6-base-6.2.4+dfsg/debian/control --- qt6-base-6.2.4+dfsg/debian/control 2022-04-11 11:33:56.0 -0600 +++ qt6-base-6.2.4+dfsg/debian/control 2022-05-02 13:21:10.0 -0600 @@ -1,7 +1,6 @@ Source: qt6-base Priority: optional -Maintainer: Ubuntu Developers -XSBC-Original-Maintainer: Debian Qt/KDE Maintainers +Maintainer: Debian Qt/KDE Maintainers Uploaders: Patrick Franz Build-Depends: cmake (>= 3.18~), debhelper-compat (= 13), diff -Nru qt6-base-6.2.4+dfsg/debian/rules qt6-base-6.2.4+dfsg/debian/rules --- qt6-base-6.2.4+dfsg/debian/rules2022-04-11 11:32:44.0 -0600 +++ qt6-base-6.2.4+dfsg/debian/rules2022-05-02 13:20:45.0 -0600 @@ -71,6 +71,7 @@ -DFEATURE_system_png=ON \ -DFEATURE_system_libb2=ON \ -DFEATURE_rpath=OFF \ + -DFEATURE_relocatable=OFF \ $(extra_cmake_args)
akonadi database creating 300MB+ log message per day
I'm seeing odd behaviour but not sure where the fault lies -- it is perhaps
some configuration issue on my part -- so asking here before filing a bug.
The file ~/.local/share/akonadi/db_data/mysql.err is being spammed by error
logs many times per minute:
2023-07-01 13:06:27 256 [ERROR] Incorrect definition of table
mysql.column_stats: expected column 'histogram' at position 10 to have type
longblob, found type varbinary(255).
2023-07-01 13:06:27 256 [ERROR] Incorrect definition of table
mysql.column_stats: expected column 'hist_type' at position 9 to have type
enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type
enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
It's accruing at the rate of several hundred MB per day. I believe it's been
going on for quite some time, because the mysql.err.old file was 35 GB by the
time I caught it.
When I search this string in google, I get lots of hits from the recent past
to many years ago that all commonly suggest that an upgrade has gone wrong.
Most of these actually deal with docker containers, but since my log file is
under akonadi I think docker is not the problem. As a test, I did shut down
docker completely and the logs still kept coming.
A typical recommendation [1] is to run "mysql_upgrade" by hand. However,
doing so gives another interesting error:
$ mysql_upgrade
Reading datadir from the MariaDB server failed. Got the following error when
executing the 'mysql' command line client
ERROR 2002 (HY000): Can't connect to local server through socket '/run/mysqld/
mysqld.sock' (2)
FATAL ERROR: Upgrade failed
In fact, the directory "/run/mysqld" doesn't even exist on the machine:
$ ls -l /run/mysqld
ls: cannot access '/run/mysqld': No such file or directory
Is this a broken config here??
Any advice gratefully accepted.
Thanks,
-Steve
[1]
https://techoverflow.net/2022/06/07/how-to-fix-docker-mariadb-correct-definition-of-table-mysql-column_stats-expected-column-hist_type-at-position-9/
signature.asc
Description: This is a digitally signed message part.
Re: akonadi database creating 300MB+ log message per day
On Saturday, July 1, 2023 1:17:56 P.M. CDT Steven Robbins wrote: > I'm seeing odd behaviour but not sure where the fault lies -- it is perhaps > some configuration issue on my part -- so asking here before filing a bug. > > The file ~/.local/share/akonadi/db_data/mysql.err is being spammed by error > logs many times per minute: I have since learned that it is kmail that is using the database: each time I click on a message, about 30 log lines are generated. Also, I should have specified that I'm running Debian unstable. -Steve signature.asc Description: This is a digitally signed message part.
Re: Re: QT target version for trixie
I appreciate the advice to target Qt 6 when possible. I'd like to switch Digikam from Qt5 to Qt6. Is there a guide to replacing package names? For example, Digikam builds with qtbase5-dev. I can't find qtbase6-dev in the archive. Am I overlooking something? Thanks, -Steve signature.asc Description: This is a digitally signed message part.
qtpaths -- is it expected to work?
Hi,
I'm maintaining digikam for Debian and -- due to ffmpeg issues -- trying to
help out with upstream development. The digikam setup script uses the
commands:
QT_INSTALL_PREFIX=`qtpaths --install-prefix`
QT_PLUGIN_INSTALL_DIR=`qtpaths --plugin-dir`
Currently both fail (on Debian unstable) with:
qtpaths: could not find a Qt installation of ''
In light of Bug #1011935 ("QtChooser is dead by choice upstream, no Qt6
Support"), I'm unsure if this is expected to work or not.
It looks like qtchooser does know about the versions installed:
$ qtchooser --list-versions
4
5
default
qt4-x86_64-linux-gnu
qt4
qt5-x86_64-linux-gnu
qt5
I thought I might be able to force a selection using the QT_SELECT variable,
but it just changes to a different error:
$ QT_SELECT=qt5 qtpaths --install-prefix
qtpaths: could not exec '/usr/lib/qt5/bin/qtpaths': No such file or directory
Thanks,
-Steve
P.S. Direct replies appreciated, not subscribed to debian-qt-kde.
signature.asc
Description: This is a digitally signed message part.
kdevelop cannot run lldb-mi
Hello, I'm trying to debug within KDevelop. When I select to debug a binary, KDevelop shows a big error message "Could not start debugger. Could not run 'lldb-mi'. Make sure that the path name is specified correctly". I can manually configure to use GDB instead of LLDB. But supposing I want to use LLDB -- what do I need to do? Oddly: the llvm-toolchain-nn changelog states that "lldb-mi" was removed in August 2019. But if so: why does KDevelop continue to use it? Elsewhere on the web, I can see that others are still using lldb-mi [1] -- is the removal a Debian thing? If so, what is the Debian thing needed for kdevelop? Thanks! -Steve [1] https://www.reddit.com/r/kde/comments/rfiwh4/ kdevelop_debug_could_not_run_lldbmi/ - signature.asc Description: This is a digitally signed message part.
Re: qtav: FTBFS with ffmpeg 5.0
Heads up for those following this bug: qtav appears to be unmaintained upstream. My only interest in the package was to enable video playback in digikam. Digikam upstream has taken most of the qtav code, incorporated into digikam source tree and fixed it up. The next release of digikam will not need qtav and therefore I will no longer be maintaining qtav. The only other usage in Debian I can find is "matrix-mirage" (which is itself orphaned). My suggestion is to simply remove qtav from Debian. If you do need qtav for some other purpose, please respond here and consider yourself the new maintainer. Best, -Steve signature.asc Description: This is a digitally signed message part.
Bug#1031953: libkf5screen8: Second monitor issues with NVIDIA
On Saturday, February 25, 2023 3:57:45 P.M. CST you wrote: > Please don’t. I plan to upload the whole of Plasma 5.27.2 targeting > bookworm. Awesome, thanks! > But please do follow-up on this and if the patch doesn’t make into the > 5.27.2 upstream release you’re welcome to report it here so we can apply > the fix on top of that release. Yep, I'll re-test and update/close the bug once 5.27.2 hits me. Best -Steve signature.asc Description: This is a digitally signed message part.
Bug#630015: kdebase-workspace-bin: KDE ignores user-specified screen resolution setting
Package: kdebase-workspace-bin Version: 4:4.6.3-1 Severity: important Tags: patch The default KDE screen resolution on my system is 1280x1024. I can successfully change this default using "System Settings / Size & Orientation" select "1600x1200", "Apply", "Save as Default" Afterwards the screen uses the new resolution 1600x1200. However, after a reboot the old screen resolution (1280x1024) will be used. Reason: o The default will be written to the configuration file $HOME/.kde/share/config/krandrrc: [Display] ApplyOnStartup=true StartupCommands="xrandr --output \"VGA-1\" --pos 0x0 --mode 1600x1200 --refresh 75 xrandr --output \"VGA-1\" --primary" [Screen_0] OutputsUnified=false UnifiedRect=0,0,0,0 UnifiedRotation=1 [Screen_0_Output_VGA-1] Active=true Rect=0,0,1600,1200 RefreshRate=75 Rotation=1 Note that the "StartupCommands" parameter consists of one string containing an embedded line-feed character. o When establishing a new session, "startkde" runs "krandrstartup" which evaluates the variable's content as follows: # new way of simply storing the commands echo -e "$krandrrc_display_startupcommands" | \ while read command; do eval "$command" done The "echo -e" command fails if the standard shell (/bin/sh) is e.g. linked to "/bin/dash", which is the default shell on my system. Reason: "-e" is not a standard option of "echo". Solution: The POSIX-conformant printf(1) command could be used instead of "echo -e" for printing a string, expanding backslash escape-characters like "\n", "\a" etc. Example: printf "%b\n" "$krandrrc_display_startupcommands" -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.iso885915, LC_CTYPE=en_US.iso885915 (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/dash Versions of packages kdebase-workspace-bin depends on: ii iso-codes 3.25.1-1 ISO language, territory, currency, ii kdebase-runtime 4:4.6.3-1runtime components from the offici ii kdebase-workspace-d 4:4.6.3-1shared data files for the KDE Plas ii kdebase-workspace-k 4:4.6.3-1KDE greet libraries for authentica ii libc6 2.13-4 Embedded GNU C Library: Shared lib ii libcln6 1.3.2-1 Class Library for Numbers (C++) ii libfontconfig1 2.8.0-2.2generic font configuration library ii libfreetype62.4.4-1 FreeType 2 font engine, shared lib ii libgcc1 1:4.6.0-10 GCC support library ii libgl1-mesa-glx [li 7.10.2-2 free implementation of the OpenGL ii libice6 2:1.0.7-1X11 Inter-Client Exchange library ii libjpeg62 6b1-1The Independent JPEG Group's JPEG ii libkcmutils44:4.6.3-3utility classes for using KCM modu ii libkde3support4 4:4.6.3-3KDE 3 Support Library for the KDE ii libkdecore5 4:4.6.3-3KDE Platform Core Library ii libkdesu5 4:4.6.3-3Console-mode Authentication Librar ii libkdeui5 4:4.6.3-3KDE Platform User Interface Librar ii libkephal4abi1 4:4.6.3-1API for easier handling of multihe ii libkfile4 4:4.6.3-3File Selection Dialog Library for ii libkidletime4 4:4.6.3-3library to provide information abo ii libkio5 4:4.6.3-3Network-enabled File Management Li ii libknewstuff3-4 4:4.6.3-3"Get Hot New Stuff" v3 Library for ii libknotifyconfig4 4:4.6.3-3library for configuring KDE Notifi ii libkparts4 4:4.6.3-3Framework for the KDE Platform Gra ii libkpty44:4.6.3-3Pseudo Terminal Library for the KD ii libkrosscore4 4:4.6.3-3Kross Core Library ii libkscreensaver54:4.6.3-1library of the KDE Screensaver sys ii libkworkspace4 4:4.6.3-1library for the kdebase workspace ii libnepomuk4 4:4.6.3-3Nepomuk Meta Data Library ii libnepomukquery4a 4:4.6.3-3Nepomuk Query Library for the KDE ii libpam0g1.1.2-3 Pluggable Authentication Modules l ii libphonon4 4:4.6.0really4.5.0-3 multimedia framework from KDE - co ii libplasma3 4:4.6.3-3Plasma Library for the KDE Platfor ii libplasmagenericshe 4:4.6.3-1shared elements for all the plasma ii libpng12-0 1.2.44-2 PNG library - runtime ii libprocesscore4abi1 4:4.6.3-1librar
KDE Package Manger
Hi everyone, I have this odd feeling that this has been asked before, but is there a KDE compatible package manager anywhere in the Debian repo's? I can't find KPackageKit or Muon. Steve -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAKn2qcVdLprFk-G9n5=w4xtn1pqgwobsetymhuj+qg6tgvb...@mail.gmail.com
kdeutils 4:4.7.4-1 FTBFS on {kfreebsd-i386,s390}
Hi, I notice a build of kdeutils 4:4.7.4-1 (for experimental) failed on kfreebsd-i386 and s390. I believe the kde4libs 4.7.4-3 upload has already fixed this problem, and that is now built+installed on these arches arches (1d 5h ago) : http://packages.debian.org/changelogs/pool/main/k/kde4libs/current/changelog#version4:4.7.4-3 So I ask that the buildd admins would queue a rebuild of this. Thank you! Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f56ae11.6010...@pyro.eu.org
koffice: FTFBS on hurd-i386
Hi, Does koffice 2.3.3-2 just need a rebuild on hurd-i386? >From the build log it seems the missing file "karbonepsimport.so" wasn't built, because the detection of pstoedit failed. That's probably because hurd-i386 had only 3.51~pre1-1 at the time (but now has 3.60-2), so I guess a rebuild would be more successful. * https://buildd.debian.org/status/fetch.php?pkg=koffice&arch=hurd-i386&ver=1%3A2.3.3-2&stamp=1312905190 Thanks, Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f653975.4000...@pyro.eu.org
Bug#900997: Different message asking for password?
Hello folks At the moment, this bug prevents a freshly installed buster with KDE as desktop to have its printers configured. If the message asking for authentication is clarified, would that be enough to at least lower the severity of this bug below RC? Kind regards -Steven
Bug#900997: print-manager: probability of package in buster?
Dear maintainers If a patch providing Antonio's proposed stop-gap message is provided, is it still possible for print-manager to get into buster? In that case, I may possibly try to hack something like that. Thanks for your work and consideration! -Steven
Bug#921552: sddm-theme-debian-maui: Maui decorations are missing after recent upgrades
Control: reassign -1 desktop-base 10.0.0 Control: severity -1 minor Control: merge -1 921678 This is actually a bug with the new "futurePrototype" theme in desktop-base, to be fixed in an imminent upload. Kind regards -Steven
Bug#922096: sddm-theme-debian-maui: background image doesn't load, shows white screen
Control: block -1 by 921678 Hi Dan I noticed this bug too, but the error is actually in desktop-base. Two other reports of this bug were already moved from sddm-theme-debian-maui to desktop-base. That makes it non-obvious from the side of sddm that the bug is known, so I will not move your report to the other package. @Aurélien: Excuse my nagging, but can this be fixed in time for the buster release? If I understand the freeze process correctly there's only little time left, right? Thank you -Steven
Bug#922096: Bug#921552: sddm-theme-debian-maui: Maui decorations are missing after recent upgrades
Control: fixed 922096 0.18.0-1 On Tue, 23 Apr 2019 23:50:52 +0200 =?ISO-8859-1?Q?Aur=E9lien_COUDERC?= wrote: > > Took a bit of time but you may have seen that the fix did land in buster by > now. :) > > > Cheers, > — > Aurélien That's better, yes. In the SDDM configuration module, the previews still don't work (haven't looked into that), but at least the login screen shows normally now. Thanks for fixing this! -Steven
Bug#980318: cantor-backend-sage: Package description inaccurate: sagemath actually is available.
Package: cantor-backend-sage Version: 4:20.12.0-1 Severity: minor Dear Maintainer, I don't use cantor or sagemath myself, but I noticed that the description of this package still claims sagemath being unavailable in Debian. Assuming the latter gets shipped in bullseye, this text should be updated. Thanks for maintaining! -Steven -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-5-amd64 (SMP w/4 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cantor-backend-sage depends on: pn cantor ii kio5.74.1-1 ii libc6 2.31-5 ii libgcc-s1 10.2.0-15 ii libkf5completion5 5.74.0-2 ii libkf5configcore5 5.74.0-2 ii libkf5configgui5 5.74.0-2 ii libkf5coreaddons5 5.74.0-2 ii libkf5i18n55.74.0-3 ii libkf5kiowidgets5 5.74.1-1 ii libkf5pty5 5.74.0-2 ii libkf5syntaxhighlighting5 5.74.0-2 ii libkf5widgetsaddons5 5.74.0-3 ii libkf5xmlgui5 5.74.0-2+b2 ii libqt5core5a 5.15.2+dfsg-2 ii libqt5gui5 5.15.2+dfsg-2 ii libqt5widgets5 5.15.2+dfsg-2 ii libstdc++6 10.2.0-15 cantor-backend-sage recommends no packages. Versions of packages cantor-backend-sage suggests: pn sagemath
Bug#458133: /usr/bin/qmake-qt4: bus error on hppa causing build failure of package Ipe
Package: libqt4-dev Version: 4.3.3-1 Severity: normal File: /usr/bin/qmake-qt4 Hello, Ipe fails to build [1], on hppa only, due to a failure of "qmake-qt4": [...] touch configure-stamp dh_testdir cd src && qmake-qt4 /bin/sh: line 1: 4492 Bus error qmake-qt4 make: *** [build-stamp] Error 138 [1] http://buildd.debian.org/fetch.cgi?&pkg=ipe&ver=6.0pre30-1&arch=hppa&stamp=1197308647&file=log -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: hppa (parisc64) Kernel: Linux 2.6.22-1-parisc64-smp (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages libqt4-dev depends on: ii libaudio-dev1.9.1-1 Network Audio System - development ii libfreetype6-dev2.3.5-1 FreeType 2 font engine, developmen ii libgl1-mesa-dev [libgl- 7.0.2-3 A free implementation of the OpenG ii libglib2.0-dev 2.14.4-2 Development files for the GLib lib ii libglu1-mesa-dev [libgl 7.0.2-3 The OpenGL utility library -- deve ii libice-dev 2:1.0.4-1X11 Inter-Client Exchange library ii libjpeg62-dev 6b-14Development files for the IJG JPEG ii libmng-dev 1.0.9-1 M-N-G library (Development headers ii libpng12-dev [libpng12- 1.2.15~beta5-3 PNG library - development ii libpq-dev 8.2.5-4 header files for libpq5 (PostgreSQ ii libqt4-core 4.3.3-1 Qt 4 core non-GUI functionality ru ii libqt4-gui 4.3.3-1 Qt 4 core GUI functionality runtim ii libqt4-qt3support 4.3.3-1 Qt 3 compatibility library for Qt ii libqt4-sql 4.3.3-1 Qt 4 SQL database module ii libsm-dev 2:1.0.3-1X11 Inter-Client Exchange library ii libsqlite0-dev 2.8.17-4 SQLite development files ii libx11-dev 2:1.0.3-7X11 client-side library (developme ii libxcursor-dev 1:1.1.9-1X cursor management library (devel ii libxext-dev 1:1.0.3-2X11 miscellaneous extensions libra ii libxft-dev 2.1.12-2 FreeType-based font drawing librar ii libxi-dev 2:1.1.3-1X11 Input extension library (devel ii libxinerama-dev 1:1.0.2-1X11 Xinerama extension library (de ii libxmu-dev 1:1.0.3-1X11 miscellaneous utility library ii libxrandr-dev 2:1.2.2-1X11 RandR extension library (devel ii libxrender-dev 1:0.9.4-1X Rendering Extension client libra ii libxt-dev 1:1.0.5-3X11 toolkit intrinsics library (de ii x11proto-core-dev 7.0.11-1 X11 core wire protocol and auxilia ii zlib1g-dev 1:1.2.3.3.dfsg-8 compression library - development Versions of packages libqt4-dev recommends: ii qt4-dev-tools 4.3.3-1Qt 4 development tools -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
