Re: Bug#585456: [digikam] please don't depend on marble-data
tags 585456 wontfix affects 585456 marble-data quit On Thu, 10 Jun 2010 12:55:41 Filipus Klutiero wrote: digikam depends on marble-data through a Depends on libmarblewidget. marble is used for geolocation, which is not used by most people Filipus, I view geolocation to be a core function for digikam, so wont disable this capability. Perhaps there is a way for marble-data to be reduced in size? Mark signature.asc Description: This is a digitally signed message part.
Bug#656839: transition: linphone libexosip2 libosip2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Debian-release, I would like to request a transition slot for linphone, libexosip2 and libosip2, for which pkg-voip-maintainers are responsible. All packages have been uploaded to experimental. linphone transition is liblinphone3 - libphone4, no external rdepends linphone provides libmediastreamer0 rdepends kopete, no binNMU required. kopete is also part of kde transition. transition libosip2-4 - libosip2-7 rdepends sipwitch siproxy libexosip all binNMU OK tranistion libexosip2-4 - libexosip2-7 rdepends sipwitch binNMU OK Mark -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash linphone (3.5.0-1) experimental; urgency=low * New upstream release [ Kilian Krause ] * Fix descriptions - thanks to Filipus Klutiero (Closes: #631227) [ Tzafrir Cohen ] * Add a dbg package. [ Mark Purcell ] * Fix please add support for armhf patch from Konstantinos (Closes: #645799) -- Mark Purcell m...@debian.org Mon, 26 Dec 2011 11:40:28 +1100 libosip2 (3.6.0-2) experimental; urgency=low * Fix Resolve unresolved symbols in shared libraries debian/rules: export EXTRA_LIB=-lpthread (Closes: #558915) -- Mark Purcell m...@debian.org Sat, 08 Oct 2011 14:06:34 +1100 libosip2 (3.6.0-1) experimental; urgency=low * New upstream release - NEW package libosip2-7 - soname bump * docs: drop duplicate-changelog-files ChangeLog * Drop content of dependancy_libs (sed -i) - Fixes Emptying dependency_libs in .la files (Closes: #64) * Switch to dh 7 * Switch to dpkg-source 3.0 (quilt) format * Upgrade to Standards Version 3.9.2 * Upgrade debian/watch to v3 * copyright-refers-to-symlink-license - Updated debian/copyright - LGPL-2.1 * Add osip.1 to libosip2-dev -- Mark Purcell m...@debian.org Sat, 08 Oct 2011 13:54:35 +1100 libosip2 (3.5.0-1) experimental; urgency=low * New upstream release * NEW package libosip2-6 - soname bump * debian/compat - 7 -- Mark Purcell m...@debian.org Sat, 29 Jan 2011 15:08:04 +1000 libexosip2 (3.6.0-1) experimental; urgency=low * New upstream release - NEW package libeXosip2-7 - soname bump * Switch to dpkg-source 3.0 (quilt) format * Switch to dh * Update to Standards Version 3.9.2 * Fix Getting rid of unneeded *.la / emptying dependency_libs debian/rules sed -i (Closes: #633180) * Fix [libexosip2-4] typo establishement in extended description Updated debian/control (Closes: #583519) * Drop binary-control-field-duplicates-source * cleanup debian/watch - debian-watch-contains-dh_make-template * Update debian/copyright GPL2 - copyright-refers-to-symlink-license -- Mark Purcell m...@debian.org Sat, 08 Oct 2011 15:20:31 +1100 libexosip2 (3.5.0-1) experimental; urgency=low * New upstream release [ Kilian Krause ] * Remove -N from wget args in get-orig-source target as -O is already used. [ Mark Purcell ] * NEW package libexosip2-6 - soname bump * Include html docs in -dev package * Build-Depends: libosip2-dev (= 3.5) -- Mark Purcell m...@debian.org Sat, 29 Jan 2011 15:37:37 +1000 -- 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/20120122052111.11965.2144.report...@acer.purcell.id.au
digikam 2.0.0 packaging for distributions
Hi,
I'm the digikam packager for Debian GNU/Linux.
I have noticed that the 2.0.0 .tar.bz2 archive from sf.net is now
including a lot of extras that were distributed separately:
docs/{kipi-plugins,digikam} will these continue to ship with the apps?
extras/kipi-plugins was previous a separate tar archive
extras/libkdcrawis also distributed with kdegraphics
extras/libkexiv2is also distributed with kdegraphics
extras/libkface is unique to digikam archive
extras/libkipi is also distributed with kdegraphics
extras/libkmap is unique to digikam archive
extras/libksane is also distributed with kdegraphics
extras/libmediawiki is unique to digikam archive
I can work around, but need to know if this is the plan for 2.0.0 final?
However, having the same libs released in the digikam archive and the
KDE SC kdegraphics archive is problematic for distributions. Especially
as some are at the same soname libkipi.so.8, whilst others have
different interfaces KDE SC 4.6 kdegraphics ships libkexiv2.so.9, whilst
digikam 2.0.0 is shipping libkexiv2.so.10.
Mark
--
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/1309615099.3152.14.camel@acer
libexiv2-9 - libexiv2-10 transition proposal
I have uploaded the new libexiv2-10 to experimental and would now like to propose the transition. exiv2 (0.21.1-1) experimental; urgency=low * New upstream release -- Mark Purcell m...@debian.org Fri, 25 Feb 2011 19:47:54 +1100 exiv2 (0.21-1) experimental; urgency=low * New upstream release (Closes: #556913, #486884, #511273) - Samsung SRW and Makernote support, API Changes * NEW package libexiv2-10 - soname bump * Update debian/control Description: -- Mark Purcell m...@debian.org Thu, 27 Jan 2011 00:05:42 +1100 Reverse Depends: ufraw ufraw-batch gimp-ufraw libstreamanalyzer0 shotwell rawstudio qtpfsgui python-pyexiv2 merkaartor libextractor-plugins krename kphotoalbum krita libkexiv2-8 gwenview kdebase-runtime hugin hugin-tools gthumb gpscorrelate gpscorrelate-gui gnome-commander libgexiv2-0 geeqie geeqie-gps libexiv2-dev libexiv2-dbg exiv2 signature.asc Description: This is a digitally signed message part
Re: kde-extras packages using kdelibs4c2a
On Sunday 27 February 2011 07:16:05 Ana Guerrero wrote: * lensfun Ana, Happy with everying except lensfun which doesn't have any kdelibs depends, so shouldn't be removed. Thanks, Mark signature.asc Description: This is a digitally signed message part.
Re: Bug#592183: linphone does not start (undefined symbol in /usr/lib/liblinphone.so.3)
On Sunday 08 August 2010 10:45:42 Y. Wei wrote: linphonec: symbol lookup error: /usr/lib/liblinphone.so.3: undefined symbol: ortp_file_exist [...] ii libortp8 3.2.1-2 Real-time Transport Protocol stack Yichun, This symbol is introduced into the later versions of libortp8. The workaround is to manually upgrade to the correct version of libortp8 The simple fix is to introduce version information for shlibs, which I will do with the next upload. The proper fix is to introduce a symbols file to track specific versions against symbols. Mark signature.asc Description: This is a digitally signed message part.
Re: [Pkg-kde-extras] Bug#585081: digikam 1.3.0 build issues.
I presume that other distributions would also have the same issues? I know that Mandriva include kdegraphics/libs from trunk as well... Sorry I don't agree that is sustainable at all. Pulling from trunk is verging on negligence for a distribution. How does Mandriva know when trunk is stable? Do they continue to patch until trunk is released? Sounds like an awful lot of work bypassing the upstream release process. If upstream have decided that work on a library is work in progress, ie they haven't released. Then why would/ should a distribution take on that risk. If libkdcraw and libkexiv2 are ready for release, but the rest of kdegraphics isn't then it is time to break them back out again, or accept the inherent delay by being a component of the larger kdegraphics release cycle. Mark signature.asc Description: This is a digitally signed message part.
Re: digikam 1.3.0 build issues.
Just compile and install libkdcraw/libkexiv2 (and also libkipi) from svn trunk (kdegraphics module) Gilles, Unfortunately for a distribution such as Debian we are tied to releases of the kdegraphics module. We can't easily include the svn trunk components of some of kdegraphics :-( all library code are managed by digiKam team. The libraries maybe managed by the digikam team, but the release is controlled by the kdegraphics release, do you know which release the updates are slated for? I would doubt that KDE SC 4.4.5 will include large changes, which means we maybe awaiting KDE SC 4.5 for updates to these libs. Previously when the digikam team released these libraries directly, we could update the library packaging independent of the upstream kdegraphics release, however we cannot do that anymore. I presume that other distributions would also have the same issues? Mark signature.asc Description: This is a digitally signed message part.
Re: library tranistion proposal exiv2(0.20): libexiv2-6 - libexiv2-9
On Tuesday 01 June 2010 07:53:23 Mark Purcell wrote: The following transition is proposed: exiv2(0.20): libexiv2-6 - libexiv2-9 As there don't appear to be any problems/ objections. I intend to upload to unstable this week. BinNMU requests to follow. Mark signature.asc Description: This is a digitally signed message part.
Re: library tranistion proposal exiv2(0.20): libexiv2-6 - libexiv2-9
On Sunday 06 June 2010 22:31:01 Adam D. Barratt wrote: Please don't upload yet. The big issue here is that we can't currently build kdebase-runtime on hppa, due to kde4libs FTBFS there (see #561203). Adam, No problem waiting, my motivation is to clear a standing issue with slow writing to Nikon cameras, which I image effects all rdepends, not just digikam: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=579835 Mark signature.asc Description: This is a digitally signed message part.
Bug#567528: python-kde4 depends errors also effect guidance-power-manager
Package: python-kde4
Version: 4:4.3.4-1+b1
Severity: normal
# aptitude install guidance-power-manager
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information... Done
Initializing package states... Done
Reading task descriptions... Done
The following NEW packages will be installed:
guidance-power-manager python-kde4{ab}
The following packages will be REMOVED:
libssh2-1-dev{u}
0 packages upgraded, 2 newly installed, 1 to remove and 16 not upgraded.
Need to get 5,467kB of archives. After unpacking 23.3MB will be used.
The following packages have unmet dependencies:
python-kde4: Depends: python-qt4 ( 4.7-2+~) but 4.7.3-1 is installed.
Depends: python-sip4 (= none) but 4.10.2-1 is installed.
-- System Information:
Debian Release: squeeze/sid
APT prefers karmic
APT policy: (500, 'karmic'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages python-kde4 depends on:
ii kdebase-runtime 4:4.4.2-1runtime components from the offici
ii kdelibs54:4.3.4-3core libraries for all KDE 4 appli
ii kdepimlibs5 4:4.4.2-1the KDE Development Platform PIM l
ii libc6 2.10.2-7 Embedded GNU C Library: Shared lib
ii libphonon4 4:4.6.0really4.4.0-3 the core library of the Phonon mul
ii libplasma3 4:4.4.2-1the Plasma Library for the KDE Pla
ii libpython2.62.6.5-2 Shared Python runtime library (ver
ii libqt4-network 4:4.6.2-4Qt 4 network module
ii libqt4-svg 4:4.6.2-4Qt 4 SVG module
ii libqt4-xml 4:4.6.2-4Qt 4 XML module
ii libqtcore4 4:4.6.2-4Qt 4 core module
ii libqtgui4 4:4.6.2-4Qt 4 GUI module
ii libsoprano4 2.4.2+dfsg.1-1 libraries for the Soprano RDF fram
ii libstdc++6 4.4.3-9 The GNU Standard C++ Library v3
ii phonon 4:4.6.0really4.4.0-3 metapackage for the Phonon multime
ii python 2.5.4-9 An interactive high-level object-o
ii python-qt4 4.7.3-1 Python bindings for Qt4
ii python-sip4 4.10.2-1 Python/C++ bindings generator runt
ii python-support 1.0.8automated rebuilding support for P
ii python2.5 2.5.5-6 An interactive high-level object-o
python-kde4 recommends no packages.
python-kde4 suggests no packages.
--
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/20100428084713.20856.76073.report...@hp.purcell.id.au
Bug#577770: RM: kdeadmin -- ROM; src:ksystemlog merged into src:kdeadmin
Package: ftp.debian.org Severity: normal There are currently two src packages providing ksystemlog in the archive: 1. The old, obsolete src:ksystemlog (0.3.2-1) [1] which is the package to be removed. 2. The new, KDE4 ksystemlog (4:4.3.4-1) [2] provided by the src:kdeadmin package that _should not_ be removed. Thanks, Mark [1] http://packages.debian.org/src:ksystemlog [2] http://packages.debian.org/src:kdeadmin -- 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/20100414113102.6435.13976.report...@hp.purcell.id.au
Re: [Bug 233674] kipi-plugins: unknown-locale-code hne i8n
On Friday 09 April 2010 08:30:14 Albert Astals Cid wrote: hm? eh? what? why would we remove a perfectly valid translation to a language spoken by 11 million people? Albert, I don't think the issue is the removal of the translations, rather the fact that the locale-code hne isn't defined in ISO 639-1 ISO 639-2. My reading of Chhattisgarhi_language[1] shows that the ISO 639-3 code is hne, whilst the ISO 639-2 code for this family is inc. I am raising this as an inconsistency. If we are accepting ISO 639-3 locales then that is fine too and we will fix lintian. Mark W: kipi-plugins: unknown-locale-code hne N: N:The package appears to ship locales for a language but uses an unknown N:locale code as a subdirectory of /usr/share/locale. This usually results N:in users of the intended target language not finding the locale. The N:language codes used in the locale directories are those from the ISO N:639-1 and ISO 639-2 standards, not those usually used as TLDs (which are N:from the ISO 3166 standard). N: N:It is possible that the language code was mistyped or incorrectly N:guessed from the language's or country's name. N: N:Refer to http://www.loc.gov/standards/iso639-2/php/code_list.php for N:details. N: N:Severity: normal, Certainty: certain N: http://lintian.debian.org/tags/unknown-locale-code.html [1] http://en.wikipedia.org/wiki/Chhattisgarhi_language signature.asc Description: This is a digitally signed message part.
Re: Bug#560893: [Bug 220236] Re: marble widget 100% CPU on exit
reassign 560893 libmarble4 4:4.3.4-1 affects 560893 digikam tag 560893 upstream fixed-upstream thanks On Thursday 31 December 2009 18:00:55 Dietz Pröpper wrote: I suspect this issue is being caused by the marble plugin widget in digikam. I second that. Downgrading marble to the version from kde 4.3.2 resolves the hang during digikam shutting down and also the cpu issue seems to have gone. http://bugs.debian.org/560893 merged-upstream: http://bugs.kde.org/show_bug.cgi?id=220236 signature.asc Description: This is a digitally signed message part.
Re: [Digikam-devel] [Bug 220236] digikam 100% CPU on exit
https://bugs.kde.org/show_bug.cgi?id=220236 On Monday 28 December 2009 11:41:23 Gilles Caulier wrote: Crash appears in marblewidget. Which version you use ? Gillies, I can also confirm this behaviour when running the standard marble application, ie without digikam. When quitting marble, the GUI closes normally, but marble continues to run at 100% in the background. Thus as you suspected the issue lies with marble, although it does effect digikam. I have also obtained a more complete backtrack, marble only, with marble symbols. Are you able to reassign this report to marblewidget in the KDE bug tracker? Mark #0 0xb7804424 in __kernel_vsyscall () #1 0xb4b1e0a5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0 #2 0xb5dba82d in pthread_cond_wait () from /lib/i686/cmov/libc.so.6 #3 0xb5fb15c2 in QWaitConditionPrivate::wait (this=0xadd7d0a0, mutex=0xadd7d08c, time=4294967295) at thread/qwaitcondition_unix.cpp:87 #4 QWaitCondition::wait (this=0xadd7d0a0, mutex=0xadd7d08c, time=4294967295) at thread/qwaitcondition_unix.cpp:159 #5 0xb5fb077b in QThread::wait (this=0xaddb0490, time=4294967295) at thread/qthread_unix.cpp:484 #6 0xb43ff69e in ~GpsdPositionProviderPlugin (this=0xadd6a600, __in_chrg=value optimized out) at ../../../../../../marble/src/plugins/positionprovider/gpsd/GpsdPositionProviderPlugin.cpp:101 #7 0xb60b004f in QObjectPrivate::deleteChildren (this=0xade00690) at kernel/qobject.cpp:1846 #8 0xb60b784b in ~QObject (this=0xade00600, __in_chrg=value optimized out) at kernel/qobject.cpp:836 #9 0xb76fb713 in ~PositionTracking (this=0xade00600, __in_chrg=value optimized out) at ../../../../marble/src/lib/gps/PositionTracking.cpp:71 #10 0xb7700c6c in ~GpsLayer (this=0x85c1cc0, __in_chrg=value optimized out) at ../../../../marble/src/lib/gps/GpsLayer.cpp:48 #11 0xb7665e2f in ~MarbleModel (this=0x8565568, __in_chrg=value optimized out) at ../../../../marble/src/lib/MarbleModel.cpp:241 #12 0xb766c2a0 in ~MarbleMap (this=0x8580718, __in_chrg=value optimized out) at ../../../../marble/src/lib/MarbleMap.cpp:377 #13 0xb7660036 in ~MarbleWidgetPrivate (this=0x859c220, __in_chrg=value optimized out) at ../../../../marble/src/lib/MarbleWidget.cpp:84 #14 ~MarbleWidget (this=0x859c220, __in_chrg=value optimized out) at ../../../../marble/src/lib/MarbleWidget.cpp:140 #15 0xb60b004f in QObjectPrivate::deleteChildren (this=0x8468508) at kernel/qobject.cpp:1846 #16 0xb65e0ceb in ~QWidget (this=0x84684f0, __in_chrg=value optimized out) at kernel/qwidget.cpp:1367 #17 0xb698b881 in ~QFrame (this=0x84684f0, __in_chrg=value optimized out) at widgets/qframe.cpp:243 #18 0xb69f3e8b in ~QSplitter (this=0x84684f0, __in_chrg=value optimized out) at widgets/qsplitter.cpp:1008 #19 0xb60b004f in QObjectPrivate::deleteChildren (this=0x8468110) at kernel/qobject.cpp:1846 #20 0xb65e0ceb in ~QWidget (this=0x8465060, __in_chrg=value optimized out) at kernel/qwidget.cpp:1367 #21 0x08054c6e in ~ControlView (this=0x8465060, __in_chrg=value optimized out) at ../../../marble/src/ControlView.cpp:62 #22 0xb77bfde0 in ~Part (this=0x8467e88, __vtt_parm=0x8077348, __in_chrg=value optimized out) at ../../kparts/part.cpp:208 #23 0xb77c010a in ~ReadOnlyPart (this=0x8467e88, __vtt_parm=0x8077344, __in_chrg=value optimized out) at ../../kparts/part.cpp:459 #24 0x080635e8 in ~MarblePart (this=0x8467e88, __in_chrg=value optimized out, __vtt_parm=value optimized out) at ../../../marble/src/marble_part.cpp:126 #25 0x0805ac84 in ~MainWindow (this=0x84623b0, __in_chrg=value optimized out, __vtt_parm=value optimized out) at ../../../marble/src/KdeMainWindow.cpp:64 #26 0xb60afd35 in qDeleteInEventHandler (o=0x1) at kernel/qobject.cpp:3814 #27 0xb60b160b in QObject::event (this=0x84623b0, e=0x8c3fb38) at kernel/qobject.cpp:1093 #28 0xb65e5300 in QWidget::event (this=0x84623b0, event=0x8c3fb38) at kernel/qwidget.cpp:7951 #29 0xb69a88f7 in QMainWindow::event (this=0x84623b0, event=0x8c3fb38) at widgets/qmainwindow.cpp:1399 #30 0xb710fbd7 in KMainWindow::event (this=0x84623b0, ev=0x8c3fb38) at ../../kdeui/widgets/kmainwindow.cpp:1101 #31 0xb715481c in KXmlGuiWindow::event (this=0x84623b0, ev=0x8c3fb38) at ../../kdeui/xmlgui/kxmlguiwindow.cpp:131 #32 0xb658fa94 in QApplicationPrivate::notify_helper (this=0x841eb30, receiver=0x84623b0, e=0x8c3fb38) at kernel/qapplication.cpp:4065 #33 0xb6597cc2 in QApplication::notify (this=0xbfd17278, receiver=0x84623b0, e=0x8c3fb38) at kernel/qapplication.cpp:4030 #34 0xb702d62d in KApplication::notify (this=0xbfd17278,
Re: library transition proposal exiv2/ libexiv2-5
On Wednesday 29 April 2009 21:33:22 Adeodato Simó wrote: Thanks a lot for your patience and cooperation, and let us know when you have uploaded to unstable. Dato, Thanks for the green light. Have now uploaded libexiv2-5 to unstable and (almost) installed on all archs. BinNMU's required for rdepends against the obsolete libexiv2-4: # apt-cache rdepends libexiv2-4 libexiv2-4 Reverse Depends: krita merkaartor kphotoalbum libkexiv2-7 hugin-tools gwenview ufraw rawstudio qtpfsgui python-pyexiv2 merkaartor libstreamanalyzer0 kphotoalbum gpscorrelate-gui gpscorrelate gnome-commander gimp-ufraw geeqie Mark signature.asc Description: This is a digitally signed message part.
Re: [Pkg-kde-extras] Bug#507235: libkipi6 from KDE4 conflicts with libkipi0
On Tuesday 21 April 2009 05:39:05 Artur R. Czechowski wrote: kphotoalbum depends on libkipi0. KDE4 provides libkipi6 which conflicts with libkipi0. Artur, This isn't actually a bug. kphotoalbum is currently a KDE3 application and is in the process of being ported to KDE4. Until then I would imagine you need to decide which you wish to have kipi0 or kipi6 applications. Mark signature.asc Description: This is a digitally signed message part.
Bug#437956: About Akregator
Update from upstream: http://akregator.kde.org/ Description: RSS/Atom feed aggregator for KDE Akregator is a news feed reader for the KDE desktop. It enables you to follow news sites, blogs and other RSS/Atom-enabled websites without the need to manually check for updates using a web browser. Akregator is designed to be both easy to use and to be powerful enough to read hundreds of news sources conveniently. It comes with Konqueror integration for adding news feeds and with an internal browser for easy news reading. . This package is part of KDE, and a component of the KDE PIM module. See the 'kde' and 'kdepim' packages for more information. signature.asc Description: This is a digitally signed message part.
Re: library transition proposal libosip2 (was: library transition proposal libortp/ liblinphone)
Hi Dato, On Saturday 07 March 2009 21:01:00 Adeodato Simó wrote: * in the first place, regarding liblinphone3 and libortp8, only linphone depends on them in testing (and are in fact provided by the same linphone source package), so any time you want to do this transition is fine, as long as it's done before KDE4 is uploaded to unstable. OK I'm keen to upload now, but would prefer to upload after libosip2-4 hits experimental as otherwise linphone would require a rebuild. * secondly, regarding libosip2-4, it is indeed a very small transition, though it would get itself tied to the ffmpeg transition via linphone. Can you upload it to experimental first to check everything rebuilds fine? libosip2-4 has been in experimental since Nov (3.2.0). There is a new upstream release available (3.3.0) but that doesn't change soname, so no transition necessary, unless I upload the new upstream to unstable. rdepends are bayonne siproxd linphone which are all good to go. Of course bayonne is also tied to the libcommoncpp2 transition ;-) But I think that is almost clear now. * finally, does the new linphone fix the FTBFSes that can be seen at https://buildd.debian.org/~luk/status/package.php?p=linphone? And, can it be uploaded without uploading libosip2-4 unstable (in case we'd need to do that)? Yes the new linphone fixes the FTBFS and does build correctly with libosip2-3. However don't we want to sequence the rdepends sourceful uploads in the correct order to minimise the revisiting of binNMUs. If I upload linphone without first clearing libosip2-4, then I will need to request a binNMU for linphone later. Or am I missing something? Thanks in advance for your answers and for contacting us, and for patiently waiting our response. A guide/ howto would be useful for this new way of working. As I couldn't find this new process documented anywhere. Something like a library transition howto: 1. soname bump? check with debian-release - await ack. 2. upload rdepends in sequence, await NEW builds on all archs until the next sequence is complete. upload next rdepends. cycle on 2 until all sourceful uploads complete 3. request bunNMU for non sourceful uploads 4. feel free to upload to experimental at any time. Mark signature.asc Description: This is a digitally signed message part.
Re: library transition proposal libosip2 (was: library transition proposal libortp/ liblinphone)
On Friday 27 February 2009 15:38:20 Mark Purcell wrote: [...] Awaiting endorsement from debian-release. Any news? Mark signature.asc Description: This is a digitally signed message part.
Re: library transition proposal libosip2 (was: library transition proposal libortp/ liblinphone)
On Friday 27 February 2009 15:38:20 Mark Purcell wrote: [...] Awaiting endorsement from debian-release. Any news? Mark signature.asc Description: This is a digitally signed message part.
library transition proposal exiv2/ libexiv2-5
Hi, I propose a transition with libexiv2-5 (already in experimental) source package exiv2. Which is a new upstream release from unstable. Could be large rdepends; libexiv2-4 Reverse Depends: krita libstreamanalyzer0 libkexiv2-7 libkexiv2-6 libkexiv2-5 kphotoalbum ufraw qtpfsgui merkaartor libstreamanalyzer0 libkexiv2-7 krita hugin-tools gwenview gthumb gimp-ufraw ufraw rawstudio qtpfsgui python-pyexiv2 merkaartor libkexiv2-3 libexiv2-dev kphotoalbum hugin-tools gwenview gpscorrelate-gui gpscorrelate gnome-commander gimp-ufraw geeqie exiv2 This also supports new upstream releases for libkexiv2 digikam (KDE3) Mark signature.asc Description: This is a digitally signed message part.
Re: library transition proposal exiv2/ libexiv2-5
On Saturday 07 March 2009 13:35:29 Mark Purcell wrote: I propose a transition with libexiv2-5 (already in experimental) source package exiv2. Which is a new upstream release from unstable. Also could I ask the rdepends (Cc:) to try the package in experimental and report back (to debian-release) if their package is ready for transition? Some data from ubuntu from Luka Renko: https://launchpad.net/~lure/+archive/ppa Build fails for the following rdepends: - gequie: uses old/private API - need to check it upstream has never version - koffice2/ krita: minor change required due to API change - will talk with upstream to fix for next beta - libkexiv2: this package should be dropped as all rdepends of it now depends on newer version from kdegraphics - pyexiv2: API change - need to check if upstream has newer version/fix Thanks, Mark signature.asc Description: This is a digitally signed message part.
Re: library transition proposal libosip2 (was: library transition proposal libortp/ liblinphone)
On Saturday 07 March 2009 16:29:55 Yasuhiro Araki wrote: Hello Mark, Hi! I am afraid I had not updated information about libosip2. No problem, just wanting to ping the issue along. Actually, renewing libosip2 package does not difficult. I have concern about side effect for some packages which depend libosip2. And I cannot check whole packages. It appears that the major reverse depends is kopete/experimental which does build correctly with the new libosip2 so I think this transition is low risk. Maybe, now is a good oppotunity to renew libosip2. Because of releasing new debian. If you have a wish to support libosip2, I would like you to take over. It seems to be working well in pkg-voip team on alioth so I wouldn't want to change that. You are still an Uploader so any contributions are welcome. Maybe this is also a good time to move sip-tester (sipp) into the pkg-voip team as well? (Bug#510663) http://dehs.alioth.debian.org/report.php?package=sip-tester Mark signature.asc Description: This is a digitally signed message part.
Re: [Fwd: Re: Fwd: [Bug 185638] digikam crash on startup]
On Monday 02 March 2009 07:12:43 you wrote: Can you confirm whether I should switch to libxine2 in stead of libxine ? See below. Luk, I don't think it is necessary. I don't have libxine2 installed and it works fine. I do agree it is probably an issue with your phonon, install especially as you are unable to get sound working correctly. Perhaps it maybe worth your while to get into #debian-kde and try and debug realtime with some of the Debian phonon ninja. There are a number of phonon-backend-[gstreamer,null,xine] which you maybe able to mix and match to get better results. But I'm rapidly getting out of my depth here. FYIW, I have the following: ii phonon 4:4.3.0-2 un phonon-backend none pn phonon-backend-gstreamer none un phonon-backend-mplayer none pn phonon-backend-null none un phonon-backend-vlc none ii phonon-backend-xine 4:4.3.0-2 ii phonon-dbg 4:4.3.0-2 Mark Originele bericht Onderwerp: Re: Fwd: [Bug 185638] digikam crash on startup Datum: Sat, 28 Feb 2009 19:48:11 +0100 Van: Gilles Caulier caulier.gil...@gmail.com Aan: Luc Castermans luc.casterm...@gmail.com Referenties: 200903010017.57831@debian.org 49a97d61.6090...@gmail.com 49a97f5d.1030...@gmail.com Le 28 février 2009 19:15, Luc Castermans luc.casterm...@gmail.com a écrit : Luc Castermans schreef: Mark Purcell schreef: http://bugs.debian.org/491458 Luc, Martial, Can you confirm you are running with libxine 1.1.16.1-2? yes, 100% match! Gilles, Just found out that there´re also libxine2 packages, do they replace libxine1 and should I use those ? Merci, Luc Good question... I don't know. Sorry Gilles signature.asc Description: This is a digitally signed message part.
Bug#517533: [Bug 185183] Aborts on initial startup
On Saturday 28 February 2009 22:56:55 Torsten Rahn wrote: Sorry, but this is a really bad solution: This will just mean that all other applications which would use the library would need to depend on the marble package as well (then the point of having a separation between the marble and the libmarble package becomes really moot ...). Thanks Torsten tackat. I understand where you are coming from. I'm actually the Debian digikam maintainer, but have opened dialog with the Debian marble maintainer(s). One thing we like to be able to do is have multiple versions of libraries installable, so when ABI changes, we don't have to rebuilt everything immediately. Would it be possible to version (soname) the plugins, to match libmarble? Alternatively given the small size of the plugins, why not just roll them up in libmarble and expose them as another API, if indeed they need exposure? Mark signature.asc Description: This is a digitally signed message part.
Bug#517533: libmarble requires plugins (.so) to operate correctly
Package: libmarble4 Version: 4:4.2.0-1 Severity: critical IIRC: [23:37] pos OK so I'll raise a grave bug, recommend that the plugins (.so) be placed in libmarble and that subsequent libmarble conflict with each other. [23:38] MoDaX pos: yeah, go ahead As currently shipped libmarble4 doesn't include the plugins (.so) they are shipped with the marble package. However applications calling libmarble4 crash if the plugins are not installed. The upstream solution is to include the plugins with the library (They aren't application specific anyways but meant for wide use). This means subseqent versions of library package need to conflict as the plugins are not versioned with soname. digikam crash without plugins installed: Application: digiKam (digikam), signal SIGSEGV [Current thread is 0 (LWP 23419)] Thread 9 (Thread 0xb3399b90 (LWP 23420)): #0 0xb7f9f424 in __kernel_vsyscall () #1 0xb51fbfb5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0 #2 0xb55f6f2d in __pthread_cond_wait (cond=0x8bae190, mutex=0x8bae178) at forward.c:139 #3 0xb57df542 in QWaitCondition::wait (this=0x8bae0b0, mutex=0x8bae0ac, time=4294967295) at thread/qwaitcondition_unix.cpp:82 #4 0x0828e879 in Digikam::ScanController::run (this=0x8bade50) at /home/mark/src/kde-extras/build-area/digikam-0.10.0~rc2/digikam/scancontroller.cpp:412 #5 0xb57de52e in QThreadPrivate::start (arg=0x8bade50) at thread/qthread_unix.cpp:185 #6 0xb51f84e5 in start_thread (arg=0xb3399b90) at pthread_create.c:297 #7 0xb55e810e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 8 (Thread 0xb204eb90 (LWP 23423)): #0 0xb7f9f424 in __kernel_vsyscall () #1 0xb51fbfb5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0 #2 0xb55f6f2d in __pthread_cond_wait (cond=0x9008c30, mutex=0x9008c18) at forward.c:139 #3 0xb57df542 in QWaitCondition::wait (this=0x8df18c0, mutex=0x8df18bc, time=4294967295) at thread/qwaitcondition_unix.cpp:82 #4 0xb71dabda in Digikam::LoadSaveThread::run (this=0x8df18b0) at /home/mark/src/kde-extras/build-area/digikam-0.10.0~rc2/libs/threadimageio/loadsavethread.cpp:131 #5 0xb57de52e in QThreadPrivate::start (arg=0x8df18b0) at thread/qthread_unix.cpp:185 #6 0xb51f84e5 in start_thread (arg=0xb204eb90) at pthread_create.c:297 #7 0xb55e810e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 7 (Thread 0xb284fb90 (LWP 23424)): #0 0xb7f9f424 in __kernel_vsyscall () #1 0xb51fbfb5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0 #2 0xb55f6f2d in __pthread_cond_wait (cond=0x8de82a0, mutex=0x8de8288) at forward.c:139 #3 0xb57df542 in QWaitCondition::wait (this=0x8deef28, mutex=0x8deef24, time=4294967295) at thread/qwaitcondition_unix.cpp:82 #4 0xb71dabda in Digikam::LoadSaveThread::run (this=0x8deef18) at /home/mark/src/kde-extras/build-area/digikam-0.10.0~rc2/libs/threadimageio/loadsavethread.cpp:131 #5 0xb57de52e in QThreadPrivate::start (arg=0x8deef18) at thread/qthread_unix.cpp:185 #6 0xb51f84e5 in start_thread (arg=0xb284fb90) at pthread_create.c:297 #7 0xb55e810e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 6 (Thread 0xaf3afb90 (LWP 23430)): #0 0xb7f9f424 in __kernel_vsyscall () #1 0xb51fc2e2 in pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_timedwait.S:179 #2 0xb55f6f84 in __pthread_cond_timedwait (cond=0x91c4100, mutex=0x91c40e8, abstime=0xaf3af36c) at forward.c:152 #3 0xb016590f in ?? () from /usr/lib/libxine.so.1 Thread 5 (Thread 0xae72db90 (LWP 23431)): #0 0xb7f9f424 in __kernel_vsyscall () #1 0xb55e05b1 in select () from /lib/i686/cmov/libc.so.6 #2 0xb018ef6e in xine_usec_sleep () from /usr/lib/libxine.so.1 #3 0x in ?? () Thread 4 (Thread 0xadf2cb90 (LWP 23432)): #0 0xb4e3e0c7 in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0 #1 0xb4e3e6ea in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x095d7b80 in ?? () #3 0xadf2c1f8 in ?? () #4 0x095d7260 in ?? () #5 0x0001 in ?? () #6 0xb4eb7a28 in ?? () from /usr/lib/libglib-2.0.so.0 #7 0xb4eb7658 in ?? () from /usr/lib/libglib-2.0.so.0 #8 0xb51fce65 in __pthread_getspecific (key=72) at pthread_getspecific.c:27 #9 0xa165 in ?? () #10 0x0048 in ?? () Thread 3 (Thread 0xad72bb90 (LWP 23435)): #0 0xb7f9f424 in __kernel_vsyscall () #1 0xb55dda37 in *__GI___poll (fds=0xad72b2c8, nfds=1, timeout=333) at ../sysdeps/unix/sysv/linux/poll.c:87 #2 0xaeb99a05 in ?? () from /usr/lib/xine/plugins/1.25/xineplug_ao_out_alsa.so #3 0xad72b2c8 in ?? () #4 0x0001 in ?? () #5 0xad72b2c8 in ?? () #6 0x in ?? () Thread 2 (Thread 0xacee8b90 (LWP 23436)): #0 0xb7f9f424 in __kernel_vsyscall () #1 0xb51fbfb5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0 #2 0xb55f6f2d in __pthread_cond_wait (cond=0x95ecde8, mutex=0x95ecdd0) at forward.c:139 #3 0xb017691a in ?? () from /usr/lib/libxine.so.1 #4 0x095ecde8 in ?? () #5
Fwd: [Bug 185638] digikam crash on startup
http://bugs.debian.org/491458 Luc, Martial, Can you confirm you are running with libxine 1.1.16.1-2? dpkg -l libxine* | grep ^i ii libxine-dev 1.1.16.1-2 ii libxine1 1.1.16.1-2 ii libxine1-bin 1.1.16.1-2 ii libxine1-console 1.1.16.1-2 ii libxine1-ffmpeg 1.1.16.1-2 ii libxine1-misc-plugins1.1.16.1-2 ii libxine1-x 1.1.16.1-2 Thanks, Mark -- Forwarded Message -- Subject: [Bug 185638] digikam crash on startup Date: Sunday 01 March 2009 From: Gilles Caulier caulier.gil...@gmail.com To: m...@debian.org https://bugs.kde.org/show_bug.cgi?id=185638 --- Comment #7 from Gilles Caulier caulier gilles gmail com 2009-02-28 14:01:18 --- This is another prblem with KDE technologies: Phonon require libxine, which have some problem currently. try to update libxine... Gilles Caulier -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You reported the bug. --- signature.asc Description: This is a digitally signed message part.
library transition proposal libosip2 (was: library transition proposal libortp/ liblinphone)
On Tuesday 24 February 2009 10:42:26 Mark Purcell wrote: liblinphone2 - liblinphone3 libortp7 - libortp8 Looks like I also have another transition to precede libortp. libosip2-3deb - libosip2-4 libosip2-3deb Reverse Depends: linphone-nox liblinphone3 siproxd siproxd linphone-nox linphone libosip2-dev liblinphone2 libexosip2-4 bayonne kopete (Cc:) looks like the only non pkg-voip transition. With linphone I have changed the -dev package to libortp-dev and Provides:/ Conflicts:/ Replaces: libortp7-dev. As a result kopete can now build as a binNMU and no source changes are necessary. Sequencing: The transition thus looks like: libosip2-4 (libosip2/3.2.0-2) - unstable (it's already in experimental) libexosip2-4 (libexosip2/3.2.0-2) - unstable (it's already in experimental) binNMU bayonne/2.3.2-3 binNMU siproxd/1:0.7.1-2 libortp8 (linphone/3.0.0-1) - unstable [new upstream release] binNMU kopete (4:4.2.0-1) in experimental but part of the KDE4.2 transition to unstable. Awaiting endorsement from debian-release. Mark -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
library transition proposal libortp/ liblinphone
Hi d-r, Planning on uploading a new version of linphone (#505566) which will also commence the following transitions: liblinphone2 - liblinphone3 libortp7 - libortp8 kopete (Cc:) looks like the only non pkg-voip transition. Mark $ apt-cache rdepends libortp7 libortp7 Reverse Depends: kopete linphone-nox linphone libortp7-dev libmediastreamer0 liblinphone2 $ apt-cache rdepends liblinphone2 liblinphone2 Reverse Depends: linphone-nox linphone liblinphone2-dev linphone-nox linphone liblinphone2-dev signature.asc Description: This is a digitally signed message part.
RE: [Pkg-kde-extras] Bug#491458: digikam: Digikam failed to start on a fresh mix debian install (lenny kde4.2 exp.)
Martial, lenny + kde4.2 isn't a supported package mix. Please upgrade to sid + kde4.2 (experimental). Mark -original message- Subject: [Pkg-kde-extras] Bug#491458: digikam: Digikam failed to start on a fresh mix debian install (lenny kde4.2 exp.) From: Martial Paupe mart...@paupe.name Date: 22/02/2009 15:01 Package: digikam Version: 2:0.10.0~rc2-1 Followup-For: Bug #491458 Hi, I've tried to install digikam on a fresh lenny install plus kde 4.2.0. Unfortunatly this doesn't work well it crash just after the splash screen. I've also attached the crash dump generated by kde. I didn't figure out if something is missing. -- System Information: Debian Release: 5.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages digikam depends on: ii kde-icons-oxygen 4:4.2.0-1 Oxygen icon theme for KDE 4 ii kdebase-runtime4:4.2.0-1 runtime components from the offici ii kdelibs5 4:4.2.0-3 core libraries for all KDE 4 appli ii kdepimlibs54:4.2.0-1 core libraries for KDE PIM 4 appli ii libc6 2.7-18GNU C Library: Shared libraries ii libgcc11:4.3.2-1.1 GCC support library ii libgphoto2-2 2.4.3-1 gphoto2 digital camera library ii libgphoto2-port0 2.4.3-1 gphoto2 digital camera port librar ii libjasper1 1.900.1-5.1 The JasPer JPEG-2000 runtime libra ii libjpeg62 6b-14 The Independent JPEG Group's JPEG ii libkdcraw7 4:4.2.0-1 Raw picture decoding C++ library ( ii libkexiv2-74:4.2.0-1 Qt like interface for the libexiv2 ii libkipi6 4:4.2.0-1 library for apps that want to use ii liblcms1 1.17.dfsg-1 Color management library ii libmarble4 4:4.2.0-1 Marble globe widget library ii libphonon4 4:4.3.0-2 Phonon multimedia framework for Qt ii libpng12-0 1.2.27-2 PNG library - runtime ii libqt4-dbus4.5.0~rc1-2 Qt 4 D-Bus module ii libqt4-network 4.5.0~rc1-2 Qt 4 network module ii libqt4-qt3support 4.5.0~rc1-2 Qt 3 compatibility library for Qt ii libqt4-sql 4.5.0~rc1-2 Qt 4 SQL module ii libqt4-sql-sqlite 4.5.0~rc1-2 Qt 4 SQLite 3 database driver ii libqt4-svg 4.5.0~rc1-2 Qt 4 SVG module ii libqt4-xml 4.5.0~rc1-2 Qt 4 XML module ii libqtcore4 4.5.0~rc1-2 Qt 4 core module ii libqtgui4 4.5.0~rc1-2 Qt 4 GUI module ii libstdc++6 4.3.2-1.1 The GNU Standard C++ Library v3 ii libtiff4 3.8.2-11 Tag Image File Format (TIFF) libra ii phonon 4:4.3.0-2 metapackage for Phonon multimedia ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime Versions of packages digikam recommends: ii konqueror 4:4.2.0-1 KDE 4's advanced file manager, web Versions of packages digikam suggests: pn digikam-doc none (no description available) -- no debconf information ___ pkg-kde-extras mailing list pkg-kde-ext...@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-kde-extras digikam.kcrash -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: digiKam 0.10.0-rc2 and kipi-plugins 0.2.0-rc2 tarballs ready to test...
On Tuesday 17 February 2009 08:49:23 you wrote: It is taking a bit more time to work on merging with Debian, as I have lots of activities in KDE KIPI Plugins (due to freeze after rc2) and Kubuntu (feature freeze in couple of days). :-( NO problem. I have pushed rc2 into Debian experimental, but we can do as many subsequent releases as we like. Also I like to work you are going upstream on kipi, so happy for your priority to be there :-) I have good and bad news: - good: I see no major difference in content between current Ubuntu package and Debian SVN (will list notable changes) Great! - bad: ubuntu uses kde4.mk and need to switch to pkg-kde-tools That could be better for a whole bunch of reasons (Cc:ed) In general, Debian package (in SVN) is the right base, but I see the following changes that can be merged from Ubuntu: - Depends: drop kde-icons-oxygen (anyway dependency through kdebase-runtime) Yes agreed. - Recommends: add kipi-plugins (well deserved as it provides a lot of functionality) Certainly. - digikamthemedesigner.manpage (missing manpage added by me) Great. - Do not ship scalable icons (svgz): they just occupy space, but not used (not sure what is debian's policy regarding this - I may also fix install rule in upstream SVN as this currently work in progress - see [1]). That isn't a problem as far as debian policy goes. I can commit the above changes to Debian SVN, but I cannot conclude on final package until I resolve Ubuntu switch to pkg-kde-tools and probably also icons changes upstream (I plan to do this in next couple of days). Great I look forward to your commits. Anyway, I still hope that with final release (planned for March 8), we will be able to just do sync from Debian instead of doing own package. I look forward to it ;-) Mark [1] http://mail.kde.org/pipermail/digikam-devel/2009-February/026587.html signature.asc Description: This is a digitally signed message part.
Bug#500540: kdebase: automounting vfat (partialy) case sensitive due to utf8 is plain wrong and dangerous
On Monday 17 November 2008 22:00:52 Heinrich Langos wrote: IMHO this is the real solution that you are looking for, but there is (or was?) a problem with making it the default. (See Message#48 for detail Hi Qt-KDE, Work on this RC bug seems to of stalled in the last couple of weeks. Could I ask what your proposed way forward for this bug for lenny? Could be worth discussing on debian-release as well. Thanks, Mark -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [Pkg-kde-extras] Bug#504490: digikam: please give a refresh do kde4 version
On Tuesday 04 November 2008 23:47:00 Eric Valette wrote: Beta5 is out as well a kipi 0.2.0 beta3. While beta2 is working for viewing images its hardly useable a icture transfers often crash and there are some db corruption as well. Eric, Thanks for the report. The issue we have is both digikam and kipi-plugins currently require libkdcraw and libkexiv2 from svn trunk ;-( Ana, Sune, should we just bite the bullet and package these libs from svn trunk, or should we await KDE 4.2, which is 'supposed' to be compatible. Mark -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#504490: Bug#504490: digikam: please give a refresh do kde4 version
On Wednesday 05 November 2008 07:52:57 Sune Vuorela wrote: I don't think we can do it in any nice way. I don't want to go kdegraphics trunk. Agreed the whole of kdegraphics would be a mess. I was more thinking along the lines that I maintain libkdcraw and libkexiv2 in s.d.o:kde-extras from trunk and upload to experimental over the top of the KDE 4.1.2 libs. Ie package as 4:4.1.2+svnXXX, then when 4.2 is released the kdegraphics libs take over again? Of course any maintenance releases against 4.1.2 would have problems, if experimental has a newer version? Personally I would prefer if the digikam folk would stick with published API's, but I have had that discussion and lost ;-( Mark -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#503985: error loading the module Embeddable Image Viewer
Package: kdelibs5 Version: 4:4.1.2-2 Severity: normal File: khtmlimagepart.so Hi all, I have been getting an missing symbol error for a little while with KDE4. When in konqueror and clicking on an embedded graphic such as: http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=5;filename=trace-small.jpg;att=1;bug=503465 I get the error dialog: There was an error loading the module Embeddable Image Viewer. The diagnostics is: QLibrary::resolve_sys: Symbol init_khtmlimagepart undefined in /usr/lib/kde4/khtmlimagepart.so (/usr/lib/kde4/khtmlimagepart.so: undefined symbol: init_khtmlimagepart) However it then goes and loads the image in the embedded viewer. So it has been pretty harmless and I was hopeing the next pulse for KDE4 would fix, but since that is a little while coming I thought I would report. I'm pretty sure I have the latest of everything from experimental Mark -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores) Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages kdelibs5 depends on: ii dbus-x11 1.2.1-4simple interprocess messaging syst ii kdelibs-bin 4:4.1.2-2 executables for all KDE 4 core app ii kdelibs5-data 4:4.1.2-2 core shared data for all KDE 4 app ii libacl1 2.2.47-2 Access control list shared library ii libaspell15 0.60.6-1 GNU Aspell spell-checker runtime l ii libattr1 1:2.4.43-1 Extended attribute shared library ii libbz2-1.01.0.5-1high-quality block-sorting file co ii libc6 2.7-15 GNU C Library: Shared libraries ii libenchant1c2a1.4.2-3.3 a wrapper library for various spel ii libfam0 2.7.0-13.3 Client library to control the FAM ii libgcc1 1:4.3.2-1 GCC support library ii libgif4 4.1.6-6library for GIF images (library) ii libice6 2:1.0.4-1 X11 Inter-Client Exchange library ii libilmbase6 1.0.1-2+nmu2 several utility libraries from ILM ii libjasper11.900.1-5.1The JasPer JPEG-2000 runtime libra ii libjpeg62 6b-14 The Independent JPEG Group's JPEG ii libkrb53 1.6.dfsg.4~beta1-4 MIT Kerberos runtime libraries ii libopenexr6 1.6.1-3runtime files for the OpenEXR imag ii libpcre3 7.8-2 Perl 5 Compatible Regular Expressi ii libphonon44:4.2.0-1 Phonon multimedia framework for Qt ii libpng12-01.2.27-2 PNG library - runtime ii libqt4-dbus 4.4.3-1Qt 4 D-Bus module ii libqt4-designer 4.4.3-1Qt 4 designer module ii libqt4-network4.4.3-1Qt 4 network module ii libqt4-qt3support 4.4.3-1Qt 3 compatibility library for Qt ii libqt4-script 4.4.3-1Qt 4 script module ii libqt4-svg4.4.3-1Qt 4 SVG module ii libqt4-xml4.4.3-1Qt 4 XML module ii libqtcore44.4.3-1Qt 4 core module ii libqtgui4 4.4.3-1Qt 4 GUI module ii libsm62:1.0.3-2 X11 Session Management library ii libsoprano4 2.1+dfsg.1-1 libraries for the Soprano RDF fram ii libssl0.9.8 0.9.8g-13 SSL shared libraries ii libstdc++64.3.2-1The GNU Standard C++ Library v3 ii libstreamanalyzer00.5.11-1 streamanalyzer library for Strigi ii libx11-6 2:1.1.5-2 X11 client-side library ii libxcursor1 1:1.1.9-1 X cursor management library ii libxfixes31:4.0.3-2 X11 miscellaneous 'fixes' extensio ii libxml2 2.6.32.dfsg-4 GNOME XML library ii libxrender1 1:0.9.4-2 X Rendering Extension client libra ii libxslt1.11.1.24-2 XSLT processing library - runtime ii libxtst6 2:1.0.3-1 X11 Testing -- Resource extension ii shared-mime-info 0.30-2 FreeDesktop.org shared MIME databa ii xauth 1:1.0.3-2 X authentication utility ii zlib1g1:1.2.3.3.dfsg-12 compression library - runtime Versions of packages kdelibs5 recommends: ii ttf-dejavu2.25-3 Metapackage to pull in ttf-dejavu- kdelibs5 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Problems from a Disitrbution End - Build issues - kipi-plugins-0.2.0-beta3.tar.bz2
Hi, I have an issue building kipi-plugins with KDE 4.1.2 in Debian. I don't expect the libdraw will be functional as that needs svn TRUNK, which the build detects, however the build then goes on to try and build anyway and blows up because the API has changed ;-( Just to echo Angelo's comments, please make the packages, even in development releases buildable against the published libs, even if additional functionality is dropped. In Debian and I presume other distros we don't wish to backport features from svn TRUNK (to echo Aaron Seigo's blog from a few days ago.) In Debian we have a sandbox called experimental where we are assembling KDE4, that has the published versions of libs in KDE 4.1.2. I too am trying to get digikam and friends into the Debian KDE4 sandbox, however the last version of digikam that is buildable against published libs is 0.10.0-beta2. kipi- plugins for KDE4 has never be buildable against published libs. I understand that digikam and friends for KDE4 is under heavy development and isn't ready for prime time, so it is actually a prime candidate for the Debian experimental sandbox, with the rest of KDE4. But we don't want to backport various things from TRUNK. There are a few early adopters in Debian and I think some useful feedback has come in the past and will continue when we can get digikam into Debian. I suspect other distros are having difficultly as are early adopter users having to pull a few things from TRUNK to build a released version of a package. So in reality digikam is missing number of beta testers that could/ should be providing valuable feedback during the development cycle for 0.10.0 So enough of the problems from the distribution end. Could I ask you to discuss during the bug sprint this weekend and potentially ensure that future versions are buildable/ stable against the published API for libs that are now part of the KDE release. Thanks, Mark PS.. here is the log failure from kipi-plugins build: [...] -- Found LibXml2: /usr/lib/libxml2.so -- Found LibXslt: /usr/lib/libxslt.so -- Found X11: /usr/lib/libX11.so -- checking for module 'libkdcraw=0.4.0' -- package 'libkdcraw=0.4.0' not found -- Found libksane: /usr/lib/libksane.so -- -- -- -- kipi-plugins 0.2.0-beta3 dependencies results http://www.kipi- plugins.org -- -- libjpeg library found... YES -- libtiff library found... YES -- libpng library found YES -- libkipi library found... YES -- libkexiv2 library found. YES -- libkdcraw library found. YES -- libksane library found.. YES (optional) -- libxml2 library found... YES (optional) -- libxslt library found... YES (optional) -- libexpat library found.. YES (optional) -- native threads support found YES
Re: Bug#502459: fixed in kdelibs 4:3.5.10.dfsg.1-1
On Friday 31 October 2008 11:19:09 Raúl Sánchez Siles wrote: 2. Convince debian-release that lenny should be released with kdelibs 3.5.10 - currently in sid.. Feel free to answer whatever doubt you may have about this issue. Comments are also welcome. Raúl, I don't disagree with what you have said, however it isn't me that you need to convince, hey I'm even part of the kde-extras team. The filtered debdiff is quite small as you say, however we are very deep into the the lenny freeze so the standard policy answer to bump minor versions of a lib would be no. Of course the risk of bumping a minor version of a important library does go up. Also every other package in lenny also has a minor version increment they will want to get included, but the point of a freeze is to stop such activity. IMHO - what the kde team would need to show to debian-release is that there are substantial benefits and low risk in including 3.5.10 at this late stage. But then again you are not suggesting an integrated 3.5.10 be included rather just one set of libs from 3.5.10 and the rest of kde stays at 3.5.9. Which again presents a level of risk. I will await further discussion on d-r, however again IMHO I don't think the present argument is strong. Which brings us back to my first option: 1. Upload a new kdelibs 3.5.9, say -7, with 63_fixed-layout-table.diff targeted at testing-proposed-updates, or I would recommend the preparation of -7 with 63_fixed-layout-table.diff now. Mark -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#502459: fixed in kdelibs 4:3.5.10.dfsg.1-1
On Monday 27 October 2008 09:17:22 Debian Qt/KDE Maintainers wrote: kdelibs (4:3.5.10.dfsg.1-1) unstable; urgency=low +++ Changes by Ana Beatriz Guerrero Lopez: [...] +++ Changes by Raúl Sánchez Siles: * konqueror: Crash on eBay page (Closes: #502459) with recently added 63_fixed-layout-table.diff Ana, Raúl et al, While the RC bug (#502459) has been fixed in sid via the upload of kdelibs 4:3.5.10.dfsg.1-1, this still leaves open the resolution of this RC bug for lenny. (4:3.5.9.dfsg.1-6) Options for resolution in lenny: 1. Upload a new kdelibs 3.5.9, say -7, with 63_fixed-layout-table.diff targeted at testing-proposed-updates, or 2. Convince debian-release that lenny should be released with kdelibs 3.5.10 - currently in experimental. I suspect that option 1 maybe more successful. Mark -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: KGoldrunner bug reports 172925 and 172926
On Saturday 18 October 2008 11:04:48 you wrote: Would you like me to try and change this, i.e. put Russell Coker as the reporter and leave you out of the loop? Or I could just CC Russell, so then you would both get feedback. Ian, Sorry for not following up and thanks for your followup with Russell. What we have is a bug reported in the first instance to the Debian bug tracking system (BTS), which the Debian maintainer of the package looks over and then if it is a Debian integration issue fixes. If it is an upstream issue, then we generally forward upstream, as I have done here. Some users, Russell in particular like to report their bugs to the Debian BTS, as they then have all their reports in one location, and the Debian maintainer can then progress. Myself I would actually prefer they did report upstream issues directly upstream and only if it is likely to effect a number of Debian users then also have an entry in the BTS. The other issue is many upstream bug trackers use a web interface and require authentication, whilst the Debian BTS is email based and thus has a lower entry cost for some users. I was unaware you were able to change the reporter in the KDE bug tracking system. Ideally the reporter would be [EMAIL PROTECTED], that way the Debian BTS would remain synced with all updates on the bug report as well. When I try and set a Cc to an arbitrary email address Bugzilla tells me it is unable to match, but I see you have managed to get russell as a Cc: How did you do that? I can recommend that you as an upstream author do subscribe (email) to the Debian Package Tracking System (PTS), or even better if you have a -devel or a -users list subscribe that to the PTS for your package. That way you will receive bugs reports as soon as they are reported and you will also be aware of the state of your package in Debian. For a package like kdegames the volume would be very low: http://packages.qa.debian.org/k/kdegames.html Mark -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Fwd: Re: Build issues; Debian, cmake, KDE4/digikam = undefined reference to `pthread_create'.
Gilles, and others,
I have received the following after discussion on the Debian lists.
Apparently this is a common case with many non-Debian build environments
linking in unnecessary libraries even if they don't need them.
In the digikam case, the fact that cImg specifically includes pthread.h means
that ${CMAKE_THREAD_LIBS_INIT} should be specifically included in
TARGET_LINK_LIBRARIES.
Mark
-- Forwarded Message --
Subject: Re: Build issues; Debian, cmake, KDE4/digikam = undefined reference
to `pthread_create'.
Date: Tue, 8 Jul 2008
From: Sune Vuorela [EMAIL PROTECTED]
To: debian-qt-kde@lists.debian.org
On Tuesday 08 July 2008 00:33:33 Mark Purcell wrote:
Hi,
I think I have come across a Debian specific issue in that digikam for kde4
doesn't link with -pthread. Others on non-Debian build enviroment report
success.
Non-debian environments recursively links everything in. This is a bug fixed
in
debian. It is slowly getting accepted by kde people.
For details, see the excessive linking thread on kde-buildsystem maillist
I find I am able to force by including ${CMAKE_THREAD_LIBS_INIT} as a
TARGET_LINK_LIBRARIES,
Yes. and this is the right thing to do. there seems to be several includes of
pthread.h in the sources, so it should specify it.
but the concensus upstream is that this should
already be pulled in by the other KDE libraries.
This is getting slowly changed. 'Cause it is a bug. It should not be pulled in
by other KDE libraries unless those other libraries *exposes* the library. I
don't think any of the kde libraries exposes pthread. (a quick way to see this
is looking at the installed header files and see that none of them is
including
a pthread header file)
I am out of my depth with cmake, so I am looking for some further Debian
assistance here.
ana/pusling have you seen this with any other KDE4 packages?
Most of them. We are fixing them one by one.
/Sune
cmake team an suggestions?
Mark
-- Forwarded Message --
Subject: Re: [Digikam-devel] 0.10.0-beta1 release tarball...
Date: Mon, 7 Jul 2008
From: Gilles Caulier [EMAIL PROTECTED]
To: digiKam developers [EMAIL PROTECTED]
2008/7/7 Mark Purcell [EMAIL PROTECTED]:
On Mon, 7 Jul 2008, Gilles Caulier wrote:
Please give me a feedback if all compile fine on your computers before
to make the official release.
Gilles,
This version still fails to link using -lpthread for me on Debian which
results in:
undefined reference to `pthread_create'.
As I mentioned yesterday I can workaround by manually patching links.txt,
during build.
Before building I have also found out how to force this inclusion in
TARGET_LINK_LIBRARIES in digikam/CMakeLists.txt:
--- digikam/CMakeLists.txt.orig 2008-07-07 22:21:31.0 +1000
+++ digikam/CMakeLists.txt 2008-07-07 21:57:05.0 +1000
@@ -117,6 +117,7 @@
${KDCRAW_LIBRARIES}
${KEXIV2_LIBRARIES}
${KIPI_LIBRARIES}
+ ${CMAKE_THREAD_LIBS_INIT}
)
IF(MARBLEWIDGET_FOUND)
I suspect that this should automatically be included, and that is why
others are having success. But for the Debian builds it appears that
-lpthread isn't included and the binary doesn't link.
${CMAKE_THREAD_LIBS_INIT} evaluates to -lpthread.
I am unsure if this is going to effect anything else though as I don't
grok CMake.
Mark
Perhaps a Debian expert can confirm a bug in CMake included in current
version ? Achim ?
Gilles Caulier
___
Digikam-devel mailing list
[EMAIL PROTECTED]
https://mail.kde.org/mailman/listinfo/digikam-devel
---
--
Genius, I cannot turn off a hard disk, how does it work?
You should log from a line over a LCD IRC case, in such way from AutoCAD you
either must open the terminale, or must unmount the utility on the
wordprocessor of a file of the device over the hardware to install a
connector.
---
signature.asc
Description: This is a digitally signed message part.
Build issues; Debian, cmake, KDE4/digikam = undefined reference to `pthread_create'.
Hi,
I think I have come across a Debian specific issue in that digikam for kde4
doesn't link with -pthread. Others on non-Debian build enviroment report
success.
I find I am able to force by including ${CMAKE_THREAD_LIBS_INIT} as a
TARGET_LINK_LIBRARIES, but the concensus upstream is that this should already
be pulled in by the other KDE libraries.
I am out of my depth with cmake, so I am looking for some further Debian
assistance here.
ana/pusling have you seen this with any other KDE4 packages?
cmake team an suggestions?
Mark
-- Forwarded Message --
Subject: Re: [Digikam-devel] 0.10.0-beta1 release tarball...
Date: Mon, 7 Jul 2008
From: Gilles Caulier [EMAIL PROTECTED]
To: digiKam developers [EMAIL PROTECTED]
2008/7/7 Mark Purcell [EMAIL PROTECTED]:
On Mon, 7 Jul 2008, Gilles Caulier wrote:
Please give me a feedback if all compile fine on your computers before
to make the official release.
Gilles,
This version still fails to link using -lpthread for me on Debian which
results in:
undefined reference to `pthread_create'.
As I mentioned yesterday I can workaround by manually patching links.txt,
during build.
Before building I have also found out how to force this inclusion in
TARGET_LINK_LIBRARIES in digikam/CMakeLists.txt:
--- digikam/CMakeLists.txt.orig 2008-07-07 22:21:31.0 +1000
+++ digikam/CMakeLists.txt 2008-07-07 21:57:05.0 +1000
@@ -117,6 +117,7 @@
${KDCRAW_LIBRARIES}
${KEXIV2_LIBRARIES}
${KIPI_LIBRARIES}
+ ${CMAKE_THREAD_LIBS_INIT}
)
IF(MARBLEWIDGET_FOUND)
I suspect that this should automatically be included, and that is why others
are having success. But for the Debian builds it appears that -lpthread
isn't included and the binary doesn't link.
${CMAKE_THREAD_LIBS_INIT} evaluates to -lpthread.
I am unsure if this is going to effect anything else though as I don't grok
CMake.
Mark
Perhaps a Debian expert can confirm a bug in CMake included in current
version ? Achim ?
Gilles Caulier
___
Digikam-devel mailing list
[EMAIL PROTECTED]
https://mail.kde.org/mailman/listinfo/digikam-devel
---
signature.asc
Description: This is a digitally signed message part.
Bug#478264: traverso: error while loading shared libraries: libQtOpenGL.so.4:
Package: traverso Version: 0.42.0-2 Severity: grave Looks like traverso's linking against libQtOpenGL isn't great ;-( $ traverso traverso: error while loading shared libraries: libQtOpenGL.so.4: cannot open shared object file: No such file or directory $ ldd /usr/bin/traverso [ ... ] libQtOpenGL.so.4 = not found Mark -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: powerpc (ppc) Kernel: Linux 2.6.18-5-powerpc Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages traverso depends on: ii libasound2 1.0.16-2 ALSA library ii libaudio2 1.9.1-2 Network Audio System - shared libr ii libc6 2.7-10GNU C Library: Shared libraries ii libfftw3-3 3.1.2-3 library for computing Fast Fourier hi libflac8 1.2.1-1.2 Free Lossless Audio Codec - runtim ii libfontconfig1 2.5.0-2 generic font configuration library ii libfreetype6 2.3.5-1 FreeType 2 font engine, shared lib ii libgcc11:4.3.0-3 GCC support library ii libgl1-mesa-glx [libgl 7.0.3-1 A free implementation of the OpenG ii libglib2.0-0 2.16.3-2 The GLib library of C routines ii libglu1-mesa [libglu1] 7.0.3-1 The OpenGL utility library (GLU) ii libice62:1.0.4-1 X11 Inter-Client Exchange library ii libjack0 0.109.2-1.1 JACK Audio Connection Kit (librari ii libmad00.15.1b-3 MPEG audio decoder library ii libogg01.1.3-3 Ogg Bitstream Library ii libpng12-0 1.2.26-1 PNG library - runtime ii libqt4-core4.4.0~rc1-4 transitional package for Qt 4 core ii libqt4-gui 4.4.0~rc1-4 Qt 4 GUI module ii libraptor1 1.4.17-1 Raptor RDF parser and serializer l ii librasqal0 0.9.15-2 Rasqal RDF query library ii librdf01.0.7-1 Redland Resource Description Frame ii libsamplerate0 0.1.3-1 audio rate conversion library ii libsm6 2:1.0.3-1+b1 X11 Session Management library ii libsndfile11.0.17-4 Library for reading/writing audio ii libstdc++6 4.3.0-3 The GNU Standard C++ Library v3 ii libvorbis0a1.2.0.dfsg-3 The Vorbis General Audio Compressi ii libvorbisenc2 1.2.0.dfsg-3 The Vorbis General Audio Compressi ii libvorbisfile3 1.2.0.dfsg-3 The Vorbis General Audio Compressi ii libwavpack14.41.0-2 an audio codec (lossy and lossless hi libx11-6 2:1.0.3-7 X11 client-side library ii libxcursor11:1.1.9-1 X cursor management library ii libxext6 2:1.0.4-1 X11 miscellaneous extension librar ii libxfixes3 1:4.0.3-2 X11 miscellaneous 'fixes' extensio ii libxi6 2:1.1.3-1 X11 Input extension library ii libxinerama1 2:1.0.3-1 X11 Xinerama extension library ii libxrandr2 2:1.2.2-1 X11 RandR extension library ii libxrender11:0.9.4-1 X Rendering Extension client libra ii libxt6 1:1.0.5-3 X11 toolkit intrinsics library ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime traverso recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#446393: kamera should Depend: on libgphoto2-2-dev for correct operation
Package: kamera Version: 4:3.5.7-4 Severity: grave KDE-Team, I know this is going to sound strange, but kamera should Depend: libgphoto2-2-dev to function correctly. We have the same issue with digikam. http://bugs.debian.org/416123 In the short term the fix for this is to Depend: on libgphoto2-2-dev, in the longer term I suspect something needs to be resolved with the .la files in libgohoto, please follow the digikam bug and upstream in bugs.kde.org Mark -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.22-2-686 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages kamera depends on: ii kdelibs4c2a 4:3.5.7.dfsg.1-7 core libraries and binaries for al ii libc6 2.6.1-5 GNU C Library: Shared libraries ii libgcc1 1:4.2.2-1GCC support library ii libgphoto2-22.4.0-7 gphoto2 digital camera library ii libgphoto2-port02.4.0-7 gphoto2 digital camera port librar ii libstdc++6 4.2.2-1 The GNU Standard C++ Library v3 kamera recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#356138: Catastrophe! - Print to File (PDF)
On Monday 15 May 2006 22:56, Pierre Habouzit wrote: Can you confirm you can print groklaw? yes I do, now I have a reproducible bug, I'll forward it upstream. Thanks, There seem to be some upstream bug reports along the same lines: http://bugs.kde.org/show_bug.cgi?id=114592 http://bugs.kde.org/show_bug.cgi?id=107991 Do you have the capability to merge upstream bugs? Mark -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#356138: Catastrophe! - Print to File (PDF)
On Monday 15 May 2006 21:44, Pierre HABOUZIT wrote: PDF impression works for me. only the 'Test' button of the PDF writer printer does not works, and throw the error you speak of, wich is minor. do you confirm it's back ? Hi Pierre, It still does not work correctly for the Test button here and you confirm it doesn't work for you for the Test button either. So the bug isn't unreproducible. If the Test button doesn't work, then I think there is something seriously wrong. I find I can print simple documents, but anything complex such as a web page with a couple of frames doesn't print correctly and reports the same error. For example http://www.groklaw.net doesn't print and returns a similar error message. Can you confirm you can print groklaw? Mark snapshot.png Description: PNG image snapshot-groklaw.png Description: PNG image
Thanks for packaging koffice!
Guys, Well done for getting koffice 1.5 into the archive as (actually) before it was released upstream.. Well done... Mark -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#356138: Catastrophe! - Print to File (PDF)
Package: kdeprint Version: 4:3.5.1-1 Severity: important Similar to #329249 I have lost the ability to print PDF documents, including from the Test button from the Printer KDE Control Module. When I hit Test... I get a Window Titled 'Catastrophe! - KNotify' with the following text: A print error occurred. Error message received from system: cupsdoprint -P 'Print to File (PDF)' -J '' -H 'localhost:631' -U 'mark' -o ' multiple-document-handling=separate-documents-uncollated-copies orientation-requested=3' '/usr/share/apps/kdeprint/testprint.ps' : execution failed with message: client-error-not-found When I try and run from the command line it appears that the printer name -P 'Print to File (PDF)' doesn't exist: [EMAIL PROTECTED]:~$ cupsdoprint -P 'Print to File (PDF)' print.ps client-error-not-found Unlike #3292249 I couldn't find any filters installed and thus haven't been able to remove them. I have purged and re-installed cups, kdeprint, gs and a few others to no effect. However upon digging further this appears to be a rerun of http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=326833 which was a QT issue and a kdelibs bug. Mark -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-686 Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1) Versions of packages kdeprint depends on: ii enscript 1.6.4-9Converts ASCII text to Postscript, ii kdelibs4c2a 4:3.5.1-3 core libraries for all KDE applica ii libc6 2.3.6-3GNU C Library: Shared libraries an ii libgcc1 1:4.0.2-10 GCC support library ii libqt3-mt 3:3.3.5-4 Qt GUI Library (Threaded runtime v ii libstdc++64.0.2-10 The GNU Standard C++ Library v3 ii poster20020830-3 Create large posters out of PostSc ii psutils 1.17-21A collection of PostScript documen Versions of packages kdeprint recommends: ii gs-esp [postscript-viewe 8.15.1.dfsg.1-1 The Ghostscript PostScript interpr ii kghostview [postscript-v 4:3.5.1-2 PostScript viewer for KDE -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337423: Patch location
For those who are looking for the upstream patch workaround.
You need to apply to /usr/include/kde/kresources/manager.h, then you can build
kopete-svn and others...
It is available here:
http://websvn.kde.org/branches/KDE/3.5/kdelibs/kresources/manager.h?rev=472457r1=465272r2=472457
--- branches/KDE/3.5/kdelibs/kresources/manager.h 2005/09/29 09:47:40
465272
+++ branches/KDE/3.5/kdelibs/kresources/manager.h 2005/10/20 20:02:38
472457
@@ -335,7 +335,7 @@
++it ) {
QString desc = mFactory-typeName( *it );
if ( !mFactory-typeDescription( *it ).isEmpty() )
- desc += ( + mFactory-typeDescription( *it ) + );
+ desc += QString::fromLatin1( () +
mFactory-typeDescription( *it ) + QString::fromLatin1());
typeDescs.append( desc );
}
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#331144: kde-extras: kmerlin has been removed from testing/unstable
Package: kde-extras Version: 5:45 Severity: normal Hi, As kmerlin has been removed from testing/unstable, it shouldn't be Recommended: by kde-extras. Thanks, Mark -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-1-686 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#285236: kaudiocreator should Recommend: vorbis-tools
Package: kaudiocreator Version: 4:3.3.1-1 Severity: normal Tags: patch --- /tmp/control.orig 2004-12-12 09:01:58.0 +1100 +++ /tmp/control2004-12-12 09:04:11.0 +1100 @@ -7,6 +7,7 @@ Source: kdemultimedia Version: 4:3.3.1-1 Depends: kdelibs4 (= 4:3.3.1), libart-2.0-2 (= 2.3.16), libartsc0 (= 1.3.1), libasound2 ( 1.0.5), libc6 (= 2.3.2.ds1-4), libfam0c102, libgcc1 (= 1:3.4.1-3), libglib2.0-0 (= 2.4.7), libice6 | xlibs ( 4.1.0), libidn11 (= 0.5.2), libkcddb1 (= 4:3.3.1), libpng12-0 (= 1.2.7), libqt3c102-mt (= 3:3.3.3), libsm6 | xlibs ( 4.1.0), libstdc++5 (= 1:3.3.4-1), libx11-6 | xlibs ( 4.1.0), libxext6 | xlibs ( 4.1.0), libxrender1, zlib1g (= 1:1.2.1), kdemultimedia-kio-plugins +Recommends: vorbis-tools Filename: pool/main/k/kdemultimedia/kaudiocreator_3.3.1-1_i386.deb Size: 145304 MD5sum: a23f3364dd781ef2b37c28ad8883f552 -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.7-1-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages kaudiocreator depends on: ii kdelibs4 4:3.3.1-1 KDE core libraries ii kdemultimedia-kio-plugins 4:3.3.1-1 Support for browsing audio CDs und ii libart-2.0-2 2.3.16-6 Library of functions for 2D graphi ii libartsc0 1.3.2-1aRts Sound system C support librar ii libasound21.0.6-5ALSA library ii libc6 2.3.2.ds1-19 GNU C Library: Shared libraries an ii libfam0c102 2.7.0-6client library to control the FAM ii libgcc1 1:3.4.3-4 GCC support library ii libglib2.0-0 2.4.8-1The GLib library of C routines ii libice6 4.3.0.dfsg.1-8 Inter-Client Exchange library ii libidn11 0.5.2-3GNU libidn library, implementation ii libkcddb1 4:3.3.1-1 cddb library for KDE ii libpng12-01.2.8rel-1 PNG library - runtime ii libqt3c102-mt 3:3.3.3-7 Qt GUI Library (Threaded runtime v ii libsm64.3.0.dfsg.1-8 X Window System Session Management ii libstdc++51:3.3.5-3 The GNU Standard C++ Library v3 ii libx11-6 4.3.0.dfsg.1-8 X Window System protocol client li ii libxext6 4.3.0.dfsg.1-8 X Window System miscellaneous exte ii libxrender1 0.8.3-7X Rendering Extension client libra ii xlibs 4.3.0.dfsg.1-8 X Window System client libraries m ii zlib1g1:1.2.2-4 compression library - runtime -- no debconf information
Bug#237260: update-menus broken for kde freedesktop-desktop-entry-spec-...
Package: kdelibs-bin Version: 4:3.2.1-1 Severity: important File: /etc/menu-methods/freedesktop-desktop-entry-spec-dirs Followup-For: Bug #237260 I can confirm that update-menus does not work here either. $ update-menus Unknown error, message=replacewith($string, $replace, $with): $replace and $with must have the same length. install-menu: /etc/menu-methods/freedesktop-desktop-entry-spec-dirs: aborting update-menus[10830]: Script /etc/menu-methods/freedesktop-desktop-entry-spec-dirs returned error status 1. Unknown error, message=replacewith($string, $replace, $with): $replace and $with must have the same length. install-menu: /etc/menu-methods/freedesktop-desktop-entry-spec-apps: aborting update-menus[10830]: Script /etc/menu-methods/freedesktop-desktop-entry-spec-apps returned error status 1. Mark -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.4.20-xfs Locale: LANG=C, LC_CTYPE=C ii menu 2.1.10-1 Provides update-menus functions for some applications Versions of packages kdelibs-bin depends on: ii kdelibs4 4:3.2.1-1 KDE core libraries ii libart-2.0-2 2.3.16-1 Library of functions for 2D graphi ii libbz2-1.01.0.2-1A high-quality block-sorting file ii libc6 2.3.2.ds1-11 GNU C Library: Shared libraries an ii libcupsys21.1.20final-16 Common UNIX Printing System(tm) - ii libfam0c102 2.7.0-5client library to control the FAM ii libgcc1 1:3.3.3-2 GCC support library ii libgcrypt11.1.12-4 LGPL Crypto library - runtime libr ii libgnutls70.8.12-5 GNU TLS library - runtime library ii libice6 4.3.0-5Inter-Client Exchange library ii libpng12-01.2.5.0-5 PNG library - runtime ii libqt3c102-mt 3:3.2.3-2 Qt GUI Library (Threaded runtime v ii libsm64.3.0-5X Window System Session Management ii libstdc++51:3.3.3-2 The GNU Standard C++ Library v3 ii libtasn1-00.1.2-1Manage ASN.1 structures (runtime) ii libx11-6 4.3.0-5X Window System protocol client li ii libxext6 4.3.0-5X Window System miscellaneous exte ii libxml2 2.6.7-1GNOME XML library ii libxrender1 0.8.3-7X Rendering Extension client libra ii libxslt1.11.1.2-3XSLT processing library - runtime ii netpbm2:10.0-3 Graphics conversion tools ii python2.3.3-7An interactive high-level object-o ii xlibs 4.3.0-5X Window System client libraries m ii zlib1g1:1.2.1-5 compression library - runtime -- no debconf information
