Bug#728819: nmu: kdenetwork_4:4.10.5-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu kdenetwork_4:4.10.5-3 . ALL . -m Rebuild against libktorrent5 With Dep-Wait on libktorrent-dev (= 1.3.1) I know that technically this is a transition but it's really a very small one: libktorrent, ktorrent and kdenetwork. I have just uploaded both libktorrent and ktorrent myself. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (110, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-1-amd64 (SMP w/4 CPU cores) Locale: LANG=lt_LT.UTF-8, LC_CTYPE=lt_LT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131105201507.4732.84859.report...@mdxdesktop.lan.vainius.eu
Bug#685284: unblock: first bunch of packages switching to xz
Hello, On 2012 m. of August 22 d., Wednesday 14:09:28 Niels Thykier wrote: It includes a new file, which I suspect is cruft (CC'ed Modestas): bugreport.cgi?msg=15;filename=0001-debian-qt-kde.mk-Use-xz-compression-by-d efault.-Clos.patch;att=1;bug=657243 So /not/ unblocked, but other than that it looks fine. Yeah, indeed, I will clean this up tonight (probably). -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201208221430.00247.mo...@debian.org
Bug#685284: unblock: first bunch of packages switching to xz
On Wednesday 22 August 2012 20:35:23 Cyril Brulebois wrote: Modestas Vainius mo...@debian.org (22/08/2012): On 2012 m. of August 22 d., Wednesday 14:09:28 Niels Thykier wrote: It includes a new file, which I suspect is cruft (CC'ed Modestas): bugreport.cgi?msg=15;filename=0001-debian-qt-kde.mk-Use-xz-compression-b y-d efault.-Clos.patch;att=1;bug=657243 So /not/ unblocked, but other than that it looks fine. Yeah, indeed, I will clean this up tonight (probably). Is there any other upload of this package planned for wheezy? If so I guess I could live with having that crufty file for a while, and get the unblock done right away. I have already uploaded 0.15.3 with cruft removed. signature.asc Description: This is a digitally signed message part.
Bug#664681: transition: KDE's 4.8 release of platform, applications and workspace
Hello, if upstream released KDE SC 4.8.5 (it could be at the end of this month or it may never happen at all), would you let it into wheezy? Upstream is focusing on 4.9 right now and 4.8.5 would really contain only (a couple of) bug fixes. It would be great to ship Wheezy with the base which is at the latest upstream stable point release. We would probably not upload everything, just important bits (a.k.a. KDE Plasma Workspaces): meta-kde kactivities kde4libs kde-runtime kdepimlibs kde-wallpapers kde-workspace kdeplasma-addons kde-baseapps and maybe a few others which we think have important bug fixes. Obviously, no SONAME changes, shlibs bumps, 3rd party package breaking or anything of the similar destructive kind will be involved, only bugfixes. signature.asc Description: This is a digitally signed message part.
Bug#664681: transition: KDE's 4.8 release of platform, applications and workspace
Hello, On šeštadienis 24 Kovas 2012 23:45:02 Sune Vuorela wrote: On Saturday 24 March 2012 22:10:07 you wrote: On Mon, Mar 19, 2012 at 22:07:22 +0100, Sune Vuorela wrote: a couple of months ago, KDE released the januar feature release Should we do the qt multiarch change before this? We can do the qt multiarch change first. we also can do it after. I would personally like to see the Qt multiarch change done, because it also brings in qt4.8 With qt4-x11 multiarch done [1] and KDE Plasma Workspaces ready in experimental [2], when could we expect a transition slot? [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653903 [ bug not closed though ] [2] http://pkg-kde.alioth.debian.org/redir/kde-sc-buildd-experimental?compact=1 -- Modestas Vainius mo...@debian.org signature.asc Description: This is a digitally signed message part.
Please schedule kdenetwork binNMUs with Dep-Wait
Hello, I have just uploaded libktorrent 1.2.0 and ktorrent 4.2.0 to unstable. libktorrent bumped SONAME in this release. The only other its reverse dependency is kget which is part of the kdenetwork source package (ongoing KDE 4.7 transition). I have verified that kdenetwork builds and works with new libktorrent. This means that libktorrent effectively becomes part of KDE transition but it should not a big deal since all depends of new libktorrent4 are in testing already (thanks to symbol files). ktorrent itself is already part of KDE transition anyway. Therefore, could you schedule kdenetwork binNMUs with Dep-Wait: libktorrent- dev (= 1.2.0) ? -- Modestas Vainius mo...@debian.org signature.asc Description: This is a digitally signed message part.
Re: Please schedule kdenetwork binNMUs with Dep-Wait
Hello, On sekmadienis 11 Kovas 2012 17:36:31 Modestas Vainius wrote: Hello, I have just uploaded libktorrent 1.2.0 and ktorrent 4.2.0 to unstable. libktorrent bumped SONAME in this release. The only other its reverse dependency is kget which is part of the kdenetwork source package (ongoing KDE 4.7 transition). I have verified that kdenetwork builds and works with new libktorrent. This means that libktorrent effectively becomes part of KDE transition but it should not a big deal since all depends of new libktorrent4 are in testing already (thanks to symbol files). ktorrent itself is already part of KDE transition anyway. Therefore, could you schedule kdenetwork binNMUs with Dep-Wait: libktorrent- dev (= 1.2.0) ? What is more, when scheduling, don't forget to --add-depends libsrtp0-dev [ia64, kfreebsd-amd64, kfreebsd-i386] as you did before (in order to workaround #662951) -- Modestas Vainius mo...@debian.org signature.asc Description: This is a digitally signed message part.
Re: Bug#632406: FTBFS: configure fails, missing 'gdcmConfigure.h'
tags 631497 fixed-upstream pending confirmed thanks Hello, On pirmadienis 04 Liepa 2011 16:52:20 Andreas Tille wrote: On Mon, Jul 04, 2011 at 03:05:30PM +0200, Cyril Brulebois wrote: tag 632406 patch thanks Philipp Kern pk...@debian.org (04/07/2011): so this would potentially block the upcoming poppler transition. We are unable to rebuild gdcm due to bug #632406 Here's a *NASTY* patch which makes gdcm build again. Please let me know if you want my NMUing it, and when. I can not speak for the medical imaging experts who usually care for this package. However, considering that this issue is blocking other packages I would consider it apropriate to issue a 0-day NMU. In case other changes are needed we might fix this in another upload. Thanks for your work on this FYI, this is a cmake bug (#631497) which will be fixed in 2.8.5 final to be released really soon. Otherwise (max. 3 days from now) I will patch cmake myself. -- Modestas Vainius modes...@vainius.eu signature.asc Description: This is a digitally signed message part.
Bug#624382: transition: KDE SC 4.6
Hello, On ketvirtadienis 28 Balandis 2011 01:59:22 Modestas Vainius wrote: I would like to ask for a slot to do the KDE SC 4.6 transition. It is already somewhat overdue (with respect to 4.6.0 release upstream) so doing it sooner (in a week or so) rather than later would be very appreciated. This transition would include immediate update of the following KDE SC and related source packages: * From 4:4.4.5 to 4:4.6.2 or later (stable 4.6.x series): meta-kde kde-l10n kde4libs kdeaccessibility kdeadmin kdeartwork kdebase kdebase-runtime kdebase-workspace kdeedu kdegames kdegraphics kdemultimedia kdenetwork kdepimlibs kdeplasma-addons kdesdk kdetoys kdeutils kdewebdev oxygen-icons * From 4:4.4.7 to 4:4.4.11 kdepim kdepim-runtime * KDE SC 4.6 dependencies: akonadi libktorrent polkit-kde-1 polkit-qt-1 So the first step is complete as of a couple of hours ago. * libopensync-plugin-kdepim is RC buggy (#569382) even if from KDE POV, binNMU should be enough. I think the package can be removed if needed. Open question what to do with it. * digikam and kipi-plugins - new upstream versions have to be packaged (I could handle that in case Mark Purcell had no time). * knights - ready to be uploaded. * konq-plugins - new upstream version will be prepared. * konq-plugins-l10n will have to be removed from the archive. * ktorrent - ready in experimental. * kdevelop, kdevelop-pg-qt, kdevelop-php, kdevplatform - new upstream versions are ready to be uploaded. This will be done in the next couple of days. Actually, konq-plugins is in unstable already. * binNMU others (I wouldn't expect them to FTBFS): nmu kmess_2.0.6.1-1 . ALL . -m KDE SC 4.6 transition nmu kphotoalbum_4.1.1-3 . ALL . -m KDE SC 4.6 transition nmu krusader_1:2.3.0~beta1-1 . ALL . -m KDE SC 4.6 transition nmu networkmanagement_0.1+git20110422.810bc16-1 . ALL . -m KDE SC 4.6 transition nmu tagua_1.0~alpha2-9 . ALL . -m KDE SC 4.6 transition nmu plasma-widget-adjustableclock_2.2-1 . ALL . -m KDE SC 4.6 transition nmu plasma-widget-smooth-tasks_0.0~wip20100227-1.1 . ALL . -m KDE SC 4.6 transition nmu kdiff3_0.9.95-7 . ALL . -m KDE SC 4.6 transition nmu plasma-widget-yawp_0.3.6-2 . ALL . -m KDE SC 4.6 transition When binNMUing, you could Dep-Wait on kde-sc-dev-latest (= 4:4.6). kde-sc- dev-latest uses Breaks to ensure that the latest KDE SC development packages are available while kde-sc-dev-latest itself is built very early in the process. So as long as Dep-Wait is not lifted until the package in question is actually installable, this should be easiest way to do binNMUs. Otherwise, if negative deps do not work, you may need to Dep-Wait = 4:4.6 on appropriate KDE development package (kdebase-workspace-dev, libkonq5-dev and others) whatever that source package needs. -- Modestas Vainius mo...@debian.org signature.asc Description: This is a digitally signed message part.
Bug#626842: pu: package kde4libs/4:4.4.5-2+squeeze2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: pu Hello, [ Disclaimer: I've already asked security team about this upload and they told me to do it via s-p-u ] The upload would fix 3 CVEs and bug #612675. Change-by-change details are below while full diff is attached. * Fix CVE-2011-1168 (Konqueror partially universal XSS in error pages) by cve_2011_1168_konqueror_xss.diff. http://git.debian.org/?p=pkg-kde/kde-sc/kde4libs.git;a=commit;h=20deb674 * Fix CVE-2010-3170 (browser wildcard cerficate validation weakness) for Konqueror by cve_2010_3170_cn_wildcards.diff. http://git.debian.org/?p=pkg-kde/kde-sc/kde4libs.git;a=commit;h=ae934a0a * Fix CVE-2011-1094 (kdelibs does not properly verify that the server hostname matches the Common Name of the Subject of an X.509 certificate if that CN is an IP address) by cve_2011_1094_ssl_verify_hostname.diff. http://git.debian.org/?p=pkg-kde/kde-sc/kde4libs.git;a=commit;h=2bfb1e47 [ kde4libs non-security changes ] * KTar: use unsigned arithmetic when calculating checksum of tar header record (as per ustar specification). However, when reading archive, verify checksum by calculating it both ways (unsigned and signed) and accept if either matches (partially solves #612675). Implemented in ktar_header_checksum_fix.diff patch. http://git.debian.org/?p=pkg-kde/kde-sc/kde4libs.git;a=commit;h=af9374ec * Fix KTar longlink support when filenames are encoded in the UTF-8 (or other multibyte) locale. Implemented in ktar_longlink_length_in_bytes.diff patch (thanks to Ibragimov Rinat). Closes: #612675 http://git.debian.org/?p=pkg-kde/kde-sc/kde4libs.git;a=commit;h=66efdda4 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (110, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-2-amd64 (SMP w/4 CPU cores) Locale: LANG=lt_LT.UTF-8, LC_CTYPE=lt_LT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff --git a/debian/changelog b/debian/changelog index 7e056e6..aac9418 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,26 @@ +kde4libs (4:4.4.5-2+squeeze2) UNRELEASED; urgency=low + + [ José Manuel Santamaría Lema ] + * Fix CVE-2011-1168 (Konqueror partially universal XSS in error pages) by +cve_2011_1168_konqueror_xss.diff. + * Fix CVE-2010-3170 (browser wildcard cerficate validation weakness) for +Konqueror by cve_2010_3170_cn_wildcards.diff. + * Fix CVE-2011-1094 (kdelibs does not properly verify that the server hostname +matches the Common Name of the Subject of an X.509 certificate if that CN is +an IP address) by cve_2011_1094_ssl_verify_hostname.diff. + + [ Modestas Vainius ] + * KTar: use unsigned arithmetic when calculating checksum of tar header record +(as per ustar specification). However, when reading archive, verify +checksum by calculating it both ways (unsigned and signed) and accept if +either matches (partially solves #612675). Implemented in +ktar_header_checksum_fix.diff patch. + * Fix KTar longlink support when filenames are encoded in the UTF-8 (or other +multibyte) locale. Implemented in ktar_longlink_length_in_bytes.diff patch +(thanks to Ibragimov Rinat). Closes: #612675 + + -- José Manuel Santamaría Lema panfa...@gmail.com Tue, 12 Apr 2011 21:16:20 +0200 + kde4libs (4:4.4.5-2+squeeze1) stable-proposed-updates; urgency=low * Add a kconf_update script (migrate_from_kde3_icon_theme) to migrate away diff --git a/debian/patches/cve_2010_3170_cn_wildcards.diff b/debian/patches/cve_2010_3170_cn_wildcards.diff new file mode 100644 index 000..640252b --- /dev/null +++ b/debian/patches/cve_2010_3170_cn_wildcards.diff @@ -0,0 +1,84 @@ +Origin: https://projects.kde.org/projects/kde/kdelibs/repository/revisions/f2a059e6 +Description: Fix wildcard ssl handling. + We now correctly handle wildcards, rather than using shell globs. This removes + the same issue as QTBUG-4455. In addition, fixes CVE-2010-3170 for Konqueror. + References: + * http://www.westpoint.ltd.uk/advisories/wp-10-0001.txt +--- a/kio/kio/tcpslavebase.cpp b/kio/kio/tcpslavebase.cpp +@@ -4,6 +4,7 @@ + * Copyright (C) 2001 Dawit Alemayehu ada...@kde.org + * Copyright (C) 2007,2008 Andreas Hartmetz ahartm...@gmail.com + * Copyright (C) 2008 Roland Harnau t...@gmx.eu ++ * Copyright (C) 2010 Richard Moore r...@kde.org + * + * This file is part of the KDE project + * +@@ -436,6 +437,49 @@ bool TCPSlaveBase::startSsl() + return startTLSInternal(KTcpSocket::TlsV1) ResultOk; + } + ++// Find out if a hostname matches an SSL certificate's Common Name (including wildcards) ++static bool isMatchingHostname(const QString cnIn, const QString hostnameIn) ++{ ++const QString cn = cnIn.toLower(); ++const QString hostname = hostnameIn.toLower(); ++ ++const int wildcard = cn.indexOf(QLatin1Char('*')); ++ ++// Check this is a wildcard
Bug#626844: pu: package kdenetwork/4:4.4.5-2+squeeze1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: pu Hello, [ Disclaimer: I've already asked security team about this upload and they told me to do it via s-p-u ] This upload would contain a patch that improves fix for CVE-2010-1000. Change-by-change details are below while full diff is attached. * Add cve_2010_1000_directory_traversal.diff, note that CVE-2010-1000 was already fixed, but this patch performs a better protection against that vulnerability. http://git.debian.org/?p=pkg-kde/kde-sc/kdenetwork.git;a=commit;h=f18dc -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (110, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-2-amd64 (SMP w/4 CPU cores) Locale: LANG=lt_LT.UTF-8, LC_CTYPE=lt_LT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff --git a/debian/changelog b/debian/changelog index 1dc6e8e..45a905d 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +kdenetwork (4:4.4.5-2+squeeze1) UNRELEASED; urgency=low + + * Add cve_2010_1000_directory_traversal.diff, note that CVE-2010-1000 was +already fixed, but this patch performs a better protection against that +vulnerability. + + -- José Manuel Santamaría Lema panfa...@gmail.com Sun, 17 Apr 2011 20:04:11 +0200 + kdenetwork (4:4.4.5-2) unstable; urgency=low * Point debian/control Vcs fields to the new Git repository. diff --git a/debian/patches/cve_2010_1000_directory_traversal.diff b/debian/patches/cve_2010_1000_directory_traversal.diff new file mode 100644 index 000..125f104 --- /dev/null +++ b/debian/patches/cve_2010_1000_directory_traversal.diff @@ -0,0 +1,21 @@ +Origin: http://websvn.kde.org/?view=revisionrevision=1227468 +Description: Further addresses CVE-2010-1000. + The file name of Metalink File is checked a better way, making it work under + more conditions. +--- a/kget/ui/metalinkcreator/metalinker.cpp b/kget/ui/metalinkcreator/metalinker.cpp +@@ -583,7 +583,13 @@ + return false; + } + +-if (name.contains(QRegExp($(\\.\\.?)?/)) || name.contains(/../) || name.endsWith(/..)) { ++if (name.endsWith('/')) { ++kError(5001) Name attribute of Metalink::File does not contain a file name: name; ++return false; ++} ++ ++const QStringList components = name.split('/'); ++if (name.startsWith('/') || components.contains(..) || components.contains(.)) { + kError(5001) Name attribute of Metalink::File contains directory traversal directives: name; + return false; + } diff --git a/debian/patches/series b/debian/patches/series index 899f203..b50afdb 100644 --- a/debian/patches/series +++ b/debian/patches/series @@ -1,3 +1,4 @@ 01_backport_use_system_libktorrent.diff 02_debian_libktorrent_porting.diff 03_kopete_icq_login_fix.diff +cve_2010_1000_directory_traversal.diff
Bug#626845: pu: package qt4-x11/4:4.6.3-4+squeeze1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: pu Hello, [ Disclaimer: I've already asked security team about this upload and they told me to do it via s-p-u ] This upload would fix 2 security issues. Change-by-change details are below while full diff is attached. * Blacklist a set of fraudulent ssl certificates; to perform this blacklisting we need these patches: - blacklist_fraudulent_comodo_certificates.diff - ssl_certificate_large_sn.diff http://git.debian.org/?p=pkg-kde/qt/qt4-x11.git;a=commit;h=f8f083cf53ff * Fix CVE-2010-3170 (browser wildcard cerficate validation weakness) with cve_2010_3170_ssl_certificates_wildcard.diff. This problem affects the Arora web browser. http://git.debian.org/?p=pkg-kde/qt/qt4-x11.git;a=commit;h=ca7ca43a374c -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (110, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-2-amd64 (SMP w/4 CPU cores) Locale: LANG=lt_LT.UTF-8, LC_CTYPE=lt_LT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff --git a/debian/changelog b/debian/changelog index bbd8811..363ab2e 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,15 @@ +qt4-x11 (4:4.6.3-4+squeeze1) UNRELEASED; urgency=low + + * Blacklist a set of fraudulent ssl certificates; to perform this +blacklisting we need these patches: +- blacklist_fraudulent_comodo_certificates.diff +- ssl_certificate_large_sn.diff + * Fix CVE-2010-3170 (browser wildcard cerficate validation weakness) with +cve_2010_3170_ssl_certificates_wildcard.diff. This problem affects the Arora +web browser. + + -- José Manuel Santamaría Lema panfa...@gmail.com Fri, 15 Apr 2011 19:13:13 +0200 + qt4-x11 (4:4.6.3-4) unstable; urgency=high [ Pino Toscano ] diff --git a/debian/patches/blacklist_fraudulent_comodo_certificates.diff b/debian/patches/blacklist_fraudulent_comodo_certificates.diff new file mode 100644 index 000..0142822 --- /dev/null +++ b/debian/patches/blacklist_fraudulent_comodo_certificates.diff @@ -0,0 +1,85 @@ +Origin: http://labs.qt.nokia.com/2011/03/29/security-advisory-fraudulent-certificates/ +Description: This patch blacklists a set of fraudulent ssl certificates. +--- a/src/network/ssl/qsslcertificate.cpp b/src/network/ssl/qsslcertificate.cpp +@@ -219,17 +219,19 @@ + Returns true if this certificate is valid; otherwise returns + false. + +-Note: Currently, this function only checks that the current ++Note: Currently, this function checks that the current + data-time is within the date-time range during which the +-certificate is considered valid. No other checks are +-currently performed. ++certificate is considered valid, and checks that the ++certificate is not in a blacklist of fraudulent certificates. + + \sa isNull() + */ + bool QSslCertificate::isValid() const + { + const QDateTime currentTime = QDateTime::currentDateTime(); +-return currentTime = d-notValidBefore currentTime = d-notValidAfter; ++return currentTime = d-notValidBefore ++currentTime = d-notValidAfter ++! QSslCertificatePrivate::isBlacklisted(*this); + } + + /*! +@@ -778,6 +780,30 @@ + return certificates; + } + ++// These certificates are known to be fraudulent and were created during the comodo ++// compromise. See http://www.comodo.com/Comodo-Fraud-Incident-2011-03-23.html ++static const char *certificate_blacklist[] = { ++04:7e:cb:e9:fc:a5:5f:7b:d0:9e:ae:36:e1:0c:ae:1e, ++f5:c8:6a:f3:61:62:f1:3a:64:f5:4f:6d:c9:58:7c:06, ++d7:55:8f:da:f5:f1:10:5b:b2:13:28:2b:70:77:29:a3, ++39:2a:43:4f:0e:07:df:1f:8a:a3:05:de:34:e0:c2:29, ++3e:75:ce:d4:6b:69:30:21:21:88:30:ae:86:a8:2a:71, ++e9:02:8b:95:78:e4:15:dc:1a:71:0a:2b:88:15:44:47, ++92:39:d5:34:8f:40:d1:69:5a:74:54:70:e1:f2:3f:43, ++b0:b7:13:3e:d0:96:f9:b5:6f:ae:91:c8:74:bd:3a:c0, ++d8:f3:5f:4e:b7:87:2b:2d:ab:06:92:e3:15:38:2f:b0, ++0 ++}; ++ ++bool QSslCertificatePrivate::isBlacklisted(const QSslCertificate certificate) ++{ ++for (int a = 0; certificate_blacklist[a] != 0; a++) { ++if (certificate.serialNumber() == certificate_blacklist[a]) ++return true; ++} ++return false; ++} ++ + #ifndef QT_NO_DEBUG_STREAM + QDebug operator(QDebug debug, const QSslCertificate certificate) + { +--- a/src/network/ssl/qsslcertificate_p.h b/src/network/ssl/qsslcertificate_p.h +@@ -96,6 +96,7 @@ + static QSslCertificate QSslCertificate_from_X509(X509 *x509); + static QListQSslCertificate certificatesFromPem(const QByteArray pem, int count = -1); + static QListQSslCertificate certificatesFromDer(const QByteArray der, int count = -1); ++static bool isBlacklisted(const QSslCertificate certificate); + + friend class QSslSocketBackendPrivate; + +--- a/src/network/ssl/qsslsocket_openssl.cpp
Bug#624647: pu: package akonadi/1.3.1-3+squeeze1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: pu Hello, Please consider accepting the patch fixing #545139 [1] to squeeze (full debdiff is below). It can be considered as regression from lenny (KDE 3) since kmail used to work fine when HOME was mounted to the network filesystem. Since KDE SC 4.4, akonadi-server is essential daemon for kmail (and other KDE Personal Information Management applications) to work. The patch addresses the issue that sockets cannot be created on the network filesystems. akonadi before this patch is only capable of creating a socket in the subdirectory of HOME. With this patch applied, it will safely create the socket in /tmp if it can't do this directly in HOME. 1.3.1-4 with this sole change has just been uploaded to unstable to get wider testing. Consider waiting a bit to see how it bares there. 1. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=545139#29 diff -u akonadi-1.3.1/debian/changelog akonadi-1.3.1/debian/changelog --- akonadi-1.3.1/debian/changelog +++ akonadi-1.3.1/debian/changelog @@ -1,3 +1,11 @@ +akonadi (1.3.1-3+squeeze1) stable-proposed-updates; urgency=low + + * Add patch 04_socket_location.diff to allow akonadi-server to run when HOME +is mounted to the network filesystem (Closes: #545139). Thanks to Ansgar +Burchardt for the patch. + + -- Modestas Vainius mo...@debian.org Sat, 30 Apr 2011 12:50:31 +0300 + akonadi (1.3.1-3) unstable; urgency=low [ Didier Raboud ] diff -u akonadi-1.3.1/debian/patches/series akonadi-1.3.1/debian/patches/series --- akonadi-1.3.1/debian/patches/series +++ akonadi-1.3.1/debian/patches/series @@ -3,0 +4 @@ +04_socket_location.diff only in patch2: unchanged: --- akonadi-1.3.1.orig/debian/patches/04_socket_location.diff +++ akonadi-1.3.1/debian/patches/04_socket_location.diff @@ -0,0 +1,251 @@ +From: Ansgar Burchardt ans...@debian.org +Date: Mon, 29 Nov 2010 12:40:18 +0100 +Subject: Move sockets away from $HOME +Bug-Debian: http://bugs.debian.org/545139 +Bug: https://bugs.kde.org/show_bug.cgi?id=179006 + +Move directories used for sockets to /tmp, using a symlink (that includes the +hostname) to remember where it is located. + +Based on upstream commit e4affdfc2922efc10b647939fd4e068c02e256eb, +includes the fix 1fa22c55fd98f29321b943605466ef4d4640de53 as well. + +--- akonadi-1.3.1.orig/server/CMakeLists.txt akonadi-1.3.1/server/CMakeLists.txt +@@ -59,6 +59,7 @@ + set(libakonadiprivate_SRCS + ${AKONADI_SHARED_SOURCES} + src/akonadi.cpp ++ src/socketdir.cpp + src/akonadiconnection.cpp + src/handler.cpp + src/handlerhelper.cpp +--- akonadi-1.3.1.orig/server/src/akonadi.cpp akonadi-1.3.1/server/src/akonadi.cpp +@@ -34,6 +34,7 @@ + #include debuginterface.h + #include storage/itemretrievalthread.h + #include preprocessormanager.h ++#include socketdir.h + + #include libs/xdgbasedirs_p.h + #include libs/protocol_p.h +@@ -84,13 +85,7 @@ + connectionSettings.setValue( QLatin1String( Data/Method ), QLatin1String( NamedPipe ) ); + connectionSettings.setValue( QLatin1String( Data/NamedPipe ), namedPipe ); + #else +-const QString defaultSocketDir = XdgBaseDirs::saveDir( data, QLatin1String( akonadi ) ); +-QString socketDir = settings.value( QLatin1String( Connection/SocketDirectory ), defaultSocketDir ).toString(); +-if ( socketDir[0] != QLatin1Char( '/' ) ) { +- QDir::home().mkdir( socketDir ); +- socketDir = QDir::homePath() + QLatin1Char( '/' ) + socketDir; +-} +- ++QString socketDir = preferredSocketDirectory( XdgBaseDirs::saveDir( data, QLatin1String( akonadi ) ) ); + const QString socketFile = socketDir + QLatin1String( /akonadiserver.socket ); + unlink( socketFile.toUtf8().constData() ); + if ( !listen( socketFile ) ) +@@ -202,8 +197,7 @@ + + #ifndef Q_OS_WIN + QSettings connectionSettings( connectionSettingsFile, QSettings::IniFormat ); +-const QString defaultSocketDir = XdgBaseDirs::saveDir( data, QLatin1String( akonadi ) ); +-const QString socketDir = settings.value( QLatin1String( Connection/SocketDirectory ), defaultSocketDir ).toString(); ++const QString socketDir = preferredSocketDirectory( XdgBaseDirs::saveDir( data, QLatin1String( akonadi ) ) ); + + if ( !QDir::home().remove( socketDir + QLatin1String( /akonadiserver.socket ) ) ) + akError() Failed to remove Unix socket; +@@ -261,7 +255,7 @@ + void AkonadiServer::startPostgresqlDatabaseProcess() + { + const QString dataDir = XdgBaseDirs::saveDir( data, QLatin1String( akonadi/db_data ) ); +- const QString socketDir = XdgBaseDirs::saveDir( data, QLatin1String( akonadi/db_misc ) ); ++ const QString socketDir = preferredSocketDirectory( XdgBaseDirs::saveDir( data, QLatin1String( akonadi/db_misc ) ) ); + + if ( !QFile::exists( QString::fromLatin1( %1/PG_VERSION ).arg( dataDir ) ) ) { + // postgre data directory not initialized yet, so call initdb on it +@@ -371,7 +365,7
Bug#624382: transition: KDE SC 4.6
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Hello, I would like to ask for a slot to do the KDE SC 4.6 transition. It is already somewhat overdue (with respect to 4.6.0 release upstream) so doing it sooner (in a week or so) rather than later would be very appreciated. This transition would include immediate update of the following KDE SC and related source packages: * From 4:4.4.5 to 4:4.6.2 or later (stable 4.6.x series): meta-kde kde-l10n kde4libs kdeaccessibility kdeadmin kdeartwork kdebase kdebase-runtime kdebase-workspace kdeedu kdegames kdegraphics kdemultimedia kdenetwork kdepimlibs kdeplasma-addons kdesdk kdetoys kdeutils kdewebdev oxygen-icons * From 4:4.4.7 to 4:4.4.11 kdepim kdepim-runtime * KDE SC 4.6 dependencies: akonadi libktorrent polkit-kde-1 polkit-qt-1 They are in experimental at the moment. What is more, packaging got some (significant) testing from some of our users while packages were provided via external repository. Even if all KDE libraries have symbol files, rebuilt external packages might still pick up new symbols via modified inline functions in the headers. Though this technique is mostly used by Qt rather than KDE so widespread shlibs bump effect is unlikely. It's not very clear to me (personally) what to do with kdebindings but IMHO if possible, it's better to delay it sometime after this transition. This ugly beast links the whole distro together. Packages that are affected by transition (and KDE dependencies which break them) are below: Michael Banck mba...@debian.org libopensync-plugin-kdepim - by kdepimlibs5/src:kdepimlibs Debian KDE Extras Team pkg-kde-ext...@lists.alioth.debian.org digikam - by libmarblewidget4/src:kdeedu libkdcraw8/src:kdegraphics libkexiv2-8/src:kdegraphics libkipi7/src:kdegraphics kipi-plugins - by libkdcraw8/src:kdegraphics libkexiv2-8/src:kdegraphics libkipi7/src:kdegraphics kmess - by libkonq5/src:kdebase knights - by libkdegames5/src:kdegames konq-plugins - by libkonq5/src:kdebase kphotoalbum - by libmarblewidget4/src:kdeedu libkdcraw8/src:kdegraphics libkipi7/src:kdegraphics krusader - by libkonq5/src:kdebase ktorrent - by libktorrent2/src:libktorrent libsolidcontrol4/src:kdebase-workspace libtaskmanager4a/src:kdebase-workspace networkmanagement - by libsolidcontrol4/src:kdebase-workspace Debian Qt/KDE Maintainers debian-qt-...@lists.debian.org kdevelop - incompatible with kde4libs 4:4.6 kdevelop-pg-qt - needed by kdevelop kdevelop-php - needs to be in sync kdevelop kdevplatform - needed by kdevelop Yann Dirson dir...@debian.org tagua - by libkdegames5/src:kdegames Davi Leal d...@gnu.org plasma-widget-adjustableclock - by libplasmaclock4a/src:kdebase-workspace Salvo Rinaldi sal...@cryptolab.net plasma-widget-smooth-tasks- by libtaskmanager4a/src:kdebase-workspace Eike Sauer e...@debian.org kdiff3- by libkonq5/src:kdebase Kai Wasserbäch cu...@debian.org plasma-widget-yawp- by libweather-ion4a/src:kdebase Tasks: * libopensync-plugin-kdepim is RC buggy (#569382) even if from KDE POV, binNMU should be enough. I think the package can be removed if needed. * digikam and kipi-plugins - new upstream versions have to be packaged (I could handle that in case Mark Purcell had no time). * knights - ready to be uploaded. * konq-plugins - new upstream version will be prepared. * konq-plugins-l10n will have to be removed from the archive. * ktorrent - ready in experimental. * kdevelop, kdevelop-pg-qt, kdevelop-php, kdevplatform - new upstream versions are ready to be uploaded. * binNMU others (I wouldn't expect them to FTBFS): nmu kmess_2.0.6.1-1 . ALL . -m KDE SC 4.6 transition nmu kphotoalbum_4.1.1-3 . ALL . -m KDE SC 4.6 transition nmu krusader_1:2.3.0~beta1-1 . ALL . -m KDE SC 4.6 transition nmu networkmanagement_0.1+git20110422.810bc16-1 . ALL . -m KDE SC 4.6 transition nmu tagua_1.0~alpha2-9 . ALL . -m KDE SC 4.6 transition nmu plasma-widget-adjustableclock_2.2-1 . ALL . -m KDE SC 4.6 transition nmu plasma-widget-smooth-tasks_0.0~wip20100227-1.1 . ALL . -m KDE SC 4.6 transition nmu kdiff3_0.9.95-7 . ALL . -m KDE SC 4.6 transition nmu plasma-widget-yawp_0.3.6-2 . ALL . -m KDE SC 4.6 transition -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (110, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux
Bug#619966: nmu: libopensync-plugin-kdepim_0.22-4
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu libopensync-plugin-kdepim_0.22-4 . ALL . -m Drop deprecated kdepimlibs5 dependency. Debian Qt/KDE team split kde(pim)libs5 packages (which used to be bundles of many libraries) with the first release from the 4.4.x series. We kept those dummy packages so transition would be granular and smooth. At the moment we are down to 2 packages (from 100+ iirc) so we are going to drop kde(pim)libs5 entirely with KDE SC 4.6 upload to Debian. Since we are beginning to test 4.6 internally, I would like kdelibs5 and kdepimlibs5 to have 0 rdepends in the archive before 4.6 hits official archive. While quassel hardcodes kdelibs5 dependency (#616026, you can't do anything about it), binNMU of libopensync-plugin-kdepim should be sufficient to drop kdepimlibs dependency. Hereby this report is a request to binNMU libopensync-plugin-kdepim. Thanks in advance. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (110, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-1-amd64 (SMP w/4 CPU cores) Locale: LANG=lt_LT.UTF-8, LC_CTYPE=lt_LT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110328171702.5491.57945.report...@mdxdesktop.lan.vainius.eu
Bug#615091: pu: package cmake/2.8.2+dsfg.1-0+squeeze1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: pu An upload of the new orig tarball (dsfg'ed) to fix #614390 in stable. Files which will be removed can be seen at [2]. Plus respective debian/copyright changes. 1. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614390 2. http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=fabdf7aa -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (110, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.37-1-amd64 (SMP w/4 CPU cores) Locale: LANG=lt_LT.UTF-8, LC_CTYPE=lt_LT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110225172047.1969.3215.report...@mdxdesktop.lan.vainius.eu
Bug#612342: squeeze KDE updates (was Re: My last (hopefully) bits for KDE in Squeeze)
Hello, On šeštadienis 12 Vasaris 2011 18:27:58 Adam D. Barratt wrote: Three would have been better; one package per report is much easier to keep track of. (As would using X-Debbugs-CC so the mail on the list actually had the bug number). Sorry, will try to do better next time. More detailed info can be found in the quoted text, individual bug reports and previous mails in the thread. 1) krunner #607974 src:kdebase-workspace. The upload is planned to be identical to the current 4:4.4.5-8 in unstable, just with squeeze-adjusted revision number. 4:4.4.5-8 fared well in unstable, I have never had a single krunner crash since upgrading. This would basically be http://websvn.kde.org/?view=revisionrevision=1098125 ? How close to the 4.5 fix is the 4.4.5 version? (There didn't appear to be a link to the backported diff in the upstream bug report). Because it was not backported by upstream, I backported it myself. But my backport is very close to the original patch. It's only an unfuzz of the modified comment lines in KDE 4.5 (see below) @@ -1,3 +1,16 @@ +From: Aaron J. Seigo ase...@kde.org +Subject: Fix for krunner occasionally crashes (threading related) +Origin: backport http://websvn.kde.org/?view=revisionrevision=1098125 +Bug: https://bugs.kde.org/show_bug.cgi?id=236496#c11 +Bug: https://bugs.kde.org/show_bug.cgi?id=224212 +Bug-Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607974 +Last-Update: 2011-01-18 +Forwarded: yes +Applied-Upstream: 4.5.0 + +move the kfileplaces usage to the main thread; really non-optimal, but KIO +forces our hand. if this works out in trunk, i'll backport to the 4.4 branch. + --- a/plasma/generic/runners/places/placesrunner.cpp +++ b/plasma/generic/runners/places/placesrunner.cpp @@ -19,14 +19,20 @@ @@ -21,16 +34,16 @@ Q_UNUSED(args) setObjectName(Places); addSyntax(Plasma::RunnerSyntax(:q:, i18n(Finds file manager locations that match :q:))); -@@ -34,7 +40,7 @@ +@@ -34,7 +40,7 @@ PlacesRunner::PlacesRunner(QObject* pare - // ensure the bookmarkmanager, etc. in the places model gets creates created in the main thread - // otherwise crashes ensue + // makes sure we have the bookmarks and what not that the places + // model uses set up in the main thread, otherwise crashes ensue -KFilePlacesModel places; +m_helper = new PlacesRunnerHelper(this); } PlacesRunner::~PlacesRunner() -@@ -43,21 +49,48 @@ +@@ -43,21 +49,48 @@ PlacesRunner::~PlacesRunner() void PlacesRunner::match(Plasma::RunnerContext context) { @@ -84,7 +97,7 @@ if ((all !text.isEmpty()) || text.compare(term, Qt::CaseInsensitive) == 0) { type = Plasma::QueryMatch::ExactMatch; relevance = all ? 0.9 : 1.0; -@@ -67,18 +100,18 @@ +@@ -67,18 +100,18 @@ void PlacesRunner::match(Plasma::RunnerC } if (type != Plasma::QueryMatch::NoMatch) { @@ -133,7 +146,7 @@ class PlacesRunner : public Plasma::AbstractRunner { Q_OBJECT -@@ -35,8 +51,14 @@ +@@ -35,8 +51,14 @@ public: void match(Plasma::RunnerContext context); void run(const Plasma::RunnerContext context, const Plasma::QueryMatch action); 2) src:krusader #604196. All info, including the patch, below and in the bug report. Package revision will be properly squeeze-adjusted. Please go ahead with this one. 3) kde4libs #588374. Squeeze upload will be based on kde4libs 4:4.4.5-3 currently in unstable. It solves a desktop defacing issues after upgrade from KDE 3 (lenny - squeeze). Quoting the changelog: * Add a kconf_update script (migrate_from_kde3_icon_theme) to migrate away from old KDE 3 icon themes which are KDE 4 incompatible (e.g. crystalsvg). (Closes: #588374) This appears not to have been included in the previous discussions, afaics? It's a shame this wasn't resolved until so close to the release, given the date of the original report. Well, I figured you would not accept non-RC fixes so I didn't even try asking. Are most themes targeted at either KDE3 or KDE4, or would they usually be expected to work with both? KDE 3 themes do not work with KDE 4. Afaik, many icons were renamed to comply with some XDG standard. So that's where defacing comes from. When KDE 4 does not find an icon in the old KDE 3 theme, it uses a default one (probably the first from the list). So in place of all missing icons, user gets the same icon all over the place (new, open, save, save as, shutdown, restart etc... buttons look the same). The patch resets icon theme in the user configuration if it does not find some KDE 4 compliant icons in the current theme. -- Modestas Vainius mo...@debian.org signature.asc Description: This is a digitally signed message part.
squeeze KDE updates (was Re: My last (hopefully) bits for KDE in Squeeze)
Package: release.debian.org User: release.debian@packages.debian.org Usertags: pu Severity: normal Hello, so I'm turning this thread into a bug report. My requests are below. More detailed info can be found in the quoted text, individual bug reports and previous mails in the thread. 1) krunner #607974 src:kdebase-workspace. The upload is planned to be identical to the current 4:4.4.5-8 in unstable, just with squeeze-adjusted revision number. 4:4.4.5-8 fared well in unstable, I have never had a single krunner crash since upgrading. 2) src:krusader #604196. All info, including the patch, below and in the bug report. Package revision will be properly squeeze-adjusted. 3) kde4libs #588374. Squeeze upload will be based on kde4libs 4:4.4.5-3 currently in unstable. It solves a desktop defacing issues after upgrade from KDE 3 (lenny - squeeze). Quoting the changelog: * Add a kconf_update script (migrate_from_kde3_icon_theme) to migrate away from old KDE 3 icon themes which are KDE 4 incompatible (e.g. crystalsvg). (Closes: #588374) * Urgency=high, the fix is solely targeted at fixing lenny-squeeze upgrades though it might not get there in time. Let me know if you could pull kdebase-workspace and kde4libs uploads directly from unstable. Or if I can start uploading. On trečiadienis 26 Sausis 2011 02:09:52 Julien Cristau wrote: On Wed, Jan 19, 2011 at 23:04:31 +0200, Modestas Vainius wrote: Hello, On trečiadienis 19 Sausis 2011 11:18:34 Julien Cristau wrote: On Tue, Jan 18, 2011 at 02:25:34 +0200, Modestas Vainius wrote: 4) src:krusader #604196 There are reports that the included fix for this grave bug is wrong. Too bad I would need to do a t-p-u upload in order to include the supposedly right fix ( http://websvn.kde.org/?view=revisionrevision=1169424 + http://websvn.kde.org/?view=revisionrevision=1169519 ). I will test it as best as I can. maybe r1 as well. First of all, some background on the issue: 1) Before 1:2.2.0~beta1-2 was uploaded, upstream [1] and me [2] had some considerations about the fix because it apparently introduced a new regression as serious as a crash [3]. To make things worse, #604196 was later opened saying that the patch didn't actually fix the bug in the end. 2) QCoreApplication::processEvents() [4] is considered to be a dangerous function when called manually. It messes up control flow in unpredictable ways as it triggers processing of the event loop right away. It may even dead lock an application in the worst case scenario (event loop processing from within unfinished event handler, oops). Who knows, maybe #604196 is because of event loop deadlock. The new patch apparently nails and fixes the real cause of the hang-on-quit. Of course if there is release process related reasons to wait (e.g. it's simply too late for t-p-u at this point), we can delay it. But if we could fix it now, we should do it (it's -1 RC bug anyway, karma++ :-)). I think this can wait for r1, and at this point I'm nervous about more changes before the release, so I'll defer this. On Tue, Jan 18, 2011 at 02:25:34 +0200, Modestas Vainius wrote: 2) krunner #607974 src:kdebase-workspace. The upstream patch http://tinyurl.com/6e6b24l is supposed to fix the crash. There is no time to confirm the fix 100% as the crash, while pretty common, is random and hard to reproduce reliably. The crash no longer occurs in KDE SC 4.5 (at least there no new reports against it upstream) which this patch is included in. I have already experienced the crash more than a dozen times. Whenever krunner goes down, it's really annoying as krunner is one of the primary UI interfaces for launching new applications in KDE. would delaying this to r1 allow to confirm the fix? 4) src:krusader #604196 There are reports that the included fix for this grave bug is wrong. Too bad I would need to do a t-p-u upload in order to include the supposedly right fix ( http://websvn.kde.org/?view=revisionrevision=1169424 + http://websvn.kde.org/?view=revisionrevision=1169519 ). I will test it as best as I can. Debdiff of the latter is bellow (#604196 is actually a dupe of #587842, but the latest discussion is in the former (#604196) bug). I tested verified the new patch, it works fine. The patch included in 1:2.2.0~beta1-2 was wrong, I removed it. $ debdiff krusader_2.2.0~beta1-2.dsc krusader_2.2.0~beta1-3.dsc diff -Nru krusader-2.2.0~beta1/debian/changelog krusader-2.2.0~beta1/debian/changelog --- krusader-2.2.0~beta1/debian/changelog 2010-10-09 03:38:41.0 +0300 +++ krusader-2.2.0~beta1/debian/changelog 2011-01-19 01:42:58.0 +0200 @@ -1,3 +1,11 @@ +krusader (1:2.2.0~beta1-3) testing-proposed-updates; urgency=high + + * Replace rev1154581.patch with backport_fix_krusader_not_terminating.diff +backported from upstream svn. It has a proper fix for #587842
Re: My last (hopefully) bits for KDE in Squeeze
Hello, On trečiadienis 19 Sausis 2011 11:18:34 Julien Cristau wrote: On Tue, Jan 18, 2011 at 02:25:34 +0200, Modestas Vainius wrote: Hello, via unstable: 1) kde (Depends: kde-full) and kde-core (Depends: kde-standard) transitional metapackages in src:meta-kde. And yes, without preinst hack, only appropriate debian/control changes. Hopefully I don't regret this (Julien knows what I'm talking about). I guess you've tested upgrades with that, and they go at least as well as without those packages :) ack. Yes, I tested. Will upload today. 2) krunner #607974 src:kdebase-workspace. The upstream patch http://tinyurl.com/6e6b24l is supposed to fix the crash. There is no time to confirm the fix 100% as the crash, while pretty common, is random and hard to reproduce reliably. The crash no longer occurs in KDE SC 4.5 (at least there no new reports against it upstream) which this patch is included in. I have already experienced the crash more than a dozen times. Whenever krunner goes down, it's really annoying as krunner is one of the primary UI interfaces for launching new applications in KDE. would delaying this to r1 allow to confirm the fix? It's tricky to reproduce so we can never be sure. We can only feel that it's fixed. For example, I tried really hard for an hour or so yesterday but I could not reproduce it. But then, when I was really in hurry, it happened to me 3 times in (almost) a row doing nothing else but trying to run kcalc! That was Murphy's law biting me very hard. Such indications are pretty typical for threading related issues. Given that everything the patch does is moves some code from the worker thread to the main GUI thread, it is very likely to be right one. After all, the code was not touched again in KDE 4.5.x cycle (past 6 months) so it should not be buggy. Therefore, I think that waiting for r1 won't do us more good as far as this bug is concerned. There are more testers in unstable rather than future stable-proposed-updates anyway and I'm definitely moving to fresher KDE soon after .0 release. I think I will upload to unstable anyway but you may choose not to unblock it (or delay unblock for some more time) if you still have some considerations. via t-p-u: 4) src:krusader #604196 There are reports that the included fix for this grave bug is wrong. Too bad I would need to do a t-p-u upload in order to include the supposedly right fix ( http://websvn.kde.org/?view=revisionrevision=1169424 + http://websvn.kde.org/?view=revisionrevision=1169519 ). I will test it as best as I can. maybe r1 as well. First of all, some background on the issue: 1) Before 1:2.2.0~beta1-2 was uploaded, upstream [1] and me [2] had some considerations about the fix because it apparently introduced a new regression as serious as a crash [3]. To make things worse, #604196 was later opened saying that the patch didn't actually fix the bug in the end. 2) QCoreApplication::processEvents() [4] is considered to be a dangerous function when called manually. It messes up control flow in unpredictable ways as it triggers processing of the event loop right away. It may even dead lock an application in the worst case scenario (event loop processing from within unfinished event handler, oops). Who knows, maybe #604196 is because of event loop deadlock. The new patch apparently nails and fixes the real cause of the hang-on-quit. Of course if there is release process related reasons to wait (e.g. it's simply too late for t-p-u at this point), we can delay it. But if we could fix it now, we should do it (it's -1 RC bug anyway, karma++ :-)). [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=587842#22 [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=587842#29 [3] http://groups.google.com/group/krusader- devel/browse_thread/thread/8f5482e3a4b2c08e/5a4495887ef76c9a see quoted text of the first message in that thread (and remaining messages). [4] http://doc.qt.nokia.com/stable/qcoreapplication.html#processEvents -- Modestas Vainius modes...@vainius.eu signature.asc Description: This is a digitally signed message part.
Re: My last (hopefully) bits for KDE in Squeeze
Hello, On antradienis 18 Sausis 2011 02:25:34 Modestas Vainius wrote: via t-p-u: 4) src:krusader #604196 There are reports that the included fix for this grave bug is wrong. Too bad I would need to do a t-p-u upload in order to include the supposedly right fix ( http://websvn.kde.org/?view=revisionrevision=1169424 + http://websvn.kde.org/?view=revisionrevision=1169519 ). I will test it as best as I can. Debdiff of the latter is bellow (#604196 is actually a dupe of #587842, but the latest discussion is in the former (#604196) bug). I tested verified the new patch, it works fine. The patch included in 1:2.2.0~beta1-2 was wrong, I removed it. $ debdiff krusader_2.2.0~beta1-2.dsc krusader_2.2.0~beta1-3.dsc diff -Nru krusader-2.2.0~beta1/debian/changelog krusader-2.2.0~beta1/debian/changelog --- krusader-2.2.0~beta1/debian/changelog 2010-10-09 03:38:41.0 +0300 +++ krusader-2.2.0~beta1/debian/changelog 2011-01-19 01:42:58.0 +0200 @@ -1,3 +1,11 @@ +krusader (1:2.2.0~beta1-3) testing-proposed-updates; urgency=high + + * Replace rev1154581.patch with backport_fix_krusader_not_terminating.diff +backported from upstream svn. It has a proper fix for #587842. +(Closes: #604196) + + -- Modestas Vainius mo...@debian.org Wed, 19 Jan 2011 01:02:53 +0200 + krusader (1:2.2.0~beta1-2) unstable; urgency=medium * Grab upstream rev1154581.patch diff -Nru krusader-2.2.0~beta1/debian/patches/backport_fix_krusader_not_terminating.diff krusader-2.2.0~beta1/debian/patches/backport_fix_krusader_not_terminating.diff --- krusader-2.2.0~beta1/debian/patches/backport_fix_krusader_not_terminating.diff 1970-01-01 03:00:00.0 +0300 +++ krusader-2.2.0~beta1/debian/patches/backport_fix_krusader_not_terminating.diff 2011-01-19 01:19:05.0 +0200 @@ -0,0 +1,88 @@ +From: Jan Lepper deht...@yahoo.de +Subject: better fix for Krusader not terminating: create panel popup on demand +Bug-Debian: http://bugs.debian.org/604196 +Forwarded: yes +Origin: backport, svn diff svn://anonsvn.kde.org/home/kde -c 1169424 + svn diff svn://anonsvn.kde.org/home/kde -c 1169519 +Last-Update: 2011-01-19 +Reviewed-By: Modestas Vainius mo...@debian.org + +--- a/krusader/Panel/listpanel.cpp b/krusader/Panel/listpanel.cpp +@@ -332,13 +332,6 @@ ListPanel::ListPanel(int typeIn, QWidget + // view + createView(); + +-// popup panel +-popup = new PanelPopup(splt, left); +-connect(popup, SIGNAL(selection(const KUrl)), SLOTS, SLOT(refresh(const KUrl))); +-connect(popup, SIGNAL(hideMe()), this, SLOT(togglePanelPopup())); +-popup-hide(); +- +- + //filter = ALL; + + // create the layout +@@ -497,6 +490,12 @@ bool ListPanel::eventFilter(QObject * wa + + void ListPanel::togglePanelPopup() + { ++if(!popup) { ++popup = new PanelPopup(splt, left); ++connect(popup, SIGNAL(selection(const KUrl)), SLOTS, SLOT(refresh(const KUrl))); ++connect(popup, SIGNAL(hideMe()), this, SLOT(togglePanelPopup())); ++} ++ + if (popup-isHidden()) { + if (popupSizes.count() 0) { + dynamic_castQSplitter*(popup-parent())-setSizes(popupSizes); +@@ -1234,7 +1233,8 @@ void ListPanel::slotJobStarted(KIO::Job* + cdUpButton-setEnabled(false); + cdOtherButton-setEnabled(false); + popupBtn-setEnabled(false); +-popup-setEnabled(false); ++if(popup) ++popup-setEnabled(false); + bookmarksButton-setEnabled(false); + historyButton-setEnabled(false); + syncBrowseButton-setEnabled(false); +@@ -1287,7 +1287,8 @@ void ListPanel::inlineRefreshListResult( + cdUpButton-setEnabled(true); + cdOtherButton-setEnabled(true); + popupBtn-setEnabled(true); +-popup-setEnabled(true); ++if(popup) ++popup-setEnabled(true); + bookmarksButton-setEnabled(true); + historyButton-setEnabled(true); + syncBrowseButton-setEnabled(true); +@@ -1358,20 +1359,22 @@ void ListPanel::editLocation() + + void ListPanel::saveSettings(KConfigGroup cfg) + { +-popup-saveSizes(); +-cfg.writeEntry(_left ? Left Panel Popup : Right Panel Popup, popup-currentPage()); ++if(popup) { ++popup-saveSizes(); ++cfg.writeEntry(_left ? Left Panel Popup : Right Panel Popup, popup-currentPage()); ++} + } + + void ListPanel::updatePopupPanel(KrViewItem *item) + { + // which panel to display on? + ListPanel *lp = 0; +-if (popup-isHidden() otherPanel-gui-popup-isHidden()) +-return; +-if (!popup-isHidden()) ++if(popup !popup-isHidden()) + lp = this; +-else if (!otherPanel-gui-popup-isHidden()) +-lp = ACTIVE_PANEL-otherPanel-gui; ++else if(otherPanel-gui-popup !otherPanel-gui-popup-isHidden()) ++lp = otherPanel-gui; ++else ++return; + + KUrl url; + if (item-name() != ..) // updir diff -Nru krusader-2.2.0~beta1/debian/patches/rev1154581.patch krusader-2.2.0~beta1/debian/patches/rev1154581.patch
My last (hopefully) bits for KDE in Squeeze
Hello, via unstable: 1) kde (Depends: kde-full) and kde-core (Depends: kde-standard) transitional metapackages in src:meta-kde. And yes, without preinst hack, only appropriate debian/control changes. Hopefully I don't regret this (Julien knows what I'm talking about). 2) krunner #607974 src:kdebase-workspace. The upstream patch http://tinyurl.com/6e6b24l is supposed to fix the crash. There is no time to confirm the fix 100% as the crash, while pretty common, is random and hard to reproduce reliably. The crash no longer occurs in KDE SC 4.5 (at least there no new reports against it upstream) which this patch is included in. I have already experienced the crash more than a dozen times. Whenever krunner goes down, it's really annoying as krunner is one of the primary UI interfaces for launching new applications in KDE. 3) akregator #605094 src:kdepim. There is a trivial one-liner fix for this crash upstream (http://websvn.kde.org/?revision=1208110view=revision, click on text changed). While the bug itself do not seem to be very urgent, I believe that prior crashes might be the main cause for #590147. via t-p-u: 4) src:krusader #604196 There are reports that the included fix for this grave bug is wrong. Too bad I would need to do a t-p-u upload in order to include the supposedly right fix ( http://websvn.kde.org/?view=revisionrevision=1169424 + http://websvn.kde.org/?view=revisionrevision=1169519 ). I will test it as best as I can. All at urgency=high. (Which) Do you ACK? -- Modestas Vainius modes...@vainius.eu signature.asc Description: This is a digitally signed message part.
Re: Requesting pre-approval to upload python-xattr to fix #609447 and #592860
Hello, On pirmadienis 10 Sausis 2011 01:26:44 Federico Ceratto wrote: Hello, I'm hereby requesting approval from the release team to upload a new version of python-xattr, meant to fix #609447 and #592860 A dependency to python-setuptools has been added to fix #609447, while #592860 required a small patch to the code to prevent a crash when listing extended attributes: FWIW, I don't see debian/control changes in the diff below. diff --git a/debian/changelog b/debian/changelog index 3a4eb78..51a0ece 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +python-xattr (0.4-5+squeeze1) testing-proposed-updates; urgency=low + + * Bugfix release: missing dependency from setuptools (Closes: #609447) + * Bugfix: xattr crashes when listing file attributes (Closes: #592860) + + -- Federico Ceratto federico.cera...@gmail.com Sun, 09 Jan 2011 17:11:11 +0100 + python-xattr (0.4-5) unstable; urgency=low * New maintainer. (Closes: #579614) diff --git a/debian/patches/series b/debian/patches/series new file mode 100644 index 000..cd49bce --- /dev/null +++ b/debian/patches/series @@ -0,0 +1 @@ +tool_long_format.diff diff --git a/debian/patches/tool_long_format.diff b/debian/patches/tool_long_format.diff new file mode 100644 index 000..33195e6 --- /dev/null +++ b/debian/patches/tool_long_format.diff @@ -0,0 +1,11 @@ +Initialize the long_format variable in tool.py +--- a/Lib/xattr/tool.py b/Lib/xattr/tool.py +@@ -38,6 +38,7 @@ + except getopt.GetoptError, e: + usage(e) + ++long_format = False + for opt, arg in optargs: + if opt in (-h, --help): + usage() -- Federico Ceratto -- Modestas Vainius mo...@debian.org signature.asc Description: This is a digitally signed message part.
Bug#608847: unblock: kdebase-workspace/4:4.4.5-6
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package kdebase-workspace Hello, this revision documents (in README.Debian) a workaround for quite annoying bug and fixes the crash on kFreeBSD that was caused by a couple of *.desktop files being wrongly ommited from kFreeBSD packages.. unblock kdebase-workspace/4:4.4.5-6 -- System Information: Debian Release: 6.0 APT prefers unstable APT policy: (500, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.36-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=lt_LT.UTF-8, LC_CTYPE=lt_LT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110103235344.22287.85250.report...@mdxdesktop.lan.vainius.eu
Bug#608147: unblock: k3b/2.0.1-1
Hello, On antradienis 28 Gruodis 2010 21:29:29 Mehdi Dogguy wrote: On 12/28/2010 08:00 PM, Modestas Vainius wrote: Hello, On antradienis 28 Gruodis 2010 12:34:40 Mehdi Dogguy wrote: +++ k3b-2.0.1/debian/k3b.bug-script 2010-07-04 07:49:00.0 + @@ -0,0 +1,7 @@ +#!/bin/sh -e + +echo +echo Gathering system configuration viai `wodim -checkdrive` (please wait)... +/usr/bin/wodim -checkdrive 3 2%3 I guess you meant 23 at the end? Unfortunately, yes :( Therefore `reportbug k3b` creates %3 file in current directory. Shall I fix it? Of course, yes! If you don't mind I will wait a couple of days. Maybe upstream will propose a good solution for #607950 in the meantime. What's more, I plan to include a straightforward one-liner patch from #587996 [1] in the upload as well. [1] diff -dupr k3b.mod/libk3bdevice/k3bdevice_mmc.cpp k3b/libk3bdevice/k3bdevice_mmc.cpp --- k3b.mod/libk3bdevice/k3bdevice_mmc.cpp 2010-09-23 12:25:34.429545279 +0200 +++ k3b/libk3bdevice/k3bdevice_mmc.cpp 2010-09-23 12:26:12.672705750 +0200 @@ -309,7 +309,7 @@ bool K3b::Device::Device::readTrackInfor // DVD-DL: 48 (MMC5) // CD: 36 (MMC2) // -if( dataLen = 4 ) { +if( dataLen = 6 ) { int m = mediaType(); if( m (MEDIA_DVD_R_DL|MEDIA_DVD_R_DL_SEQ|MEDIA_DVD_R_DL_JUMP) ) dataLen = 48; -- Modestas Vainius mo...@debian.org signature.asc Description: This is a digitally signed message part.
Bug#608147: unblock: k3b/2.0.1-1
Hello, On trečiadienis 29 Gruodis 2010 22:37:55 Mehdi Dogguy wrote: On 12/29/2010 09:25 PM, Modestas Vainius wrote: If you don't mind I will wait a couple of days. Maybe upstream will propose a good solution for #607950 in the meantime. What's more, I plan to include a straightforward one-liner patch from #587996 [1] in the upload as well. Well, no. Both bugs are found in testing's version. So, there is no reason to wait for. So, Please get the reportbug script fixed, include the patch for #587996 and upload. We will see for #607950 later. Ok, uploaded [1][2]. [1] http://packages.qa.debian.org/k/k3b/news/20101229T213406Z.html [2] http://incoming.debian.org/k3b_2.0.1-2.dsc -- Modestas Vainius mo...@debian.org signature.asc Description: This is a digitally signed message part.
Bug#608147: unblock: k3b/2.0.1-1
Hello, On antradienis 28 Gruodis 2010 12:34:40 Mehdi Dogguy wrote: +++ k3b-2.0.1/debian/k3b.bug-script 2010-07-04 07:49:00.0 + @@ -0,0 +1,7 @@ +#!/bin/sh -e + +echo +echo Gathering system configuration viai `wodim -checkdrive` (please wait)... +/usr/bin/wodim -checkdrive 3 2%3 I guess you meant 23 at the end? Unfortunately, yes :( Therefore `reportbug k3b` creates %3 file in current directory. Shall I fix it? -- Modestas Vainius mo...@debian.org signature.asc Description: This is a digitally signed message part.
Bug#608147: unblock: k3b/2.0.1-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package k3b I'm requesting this unblock for a couple of reasons: 1) New upstream is bug-fix only. 2.0.1 = Bugfixes: * Freeze on ripping Audio CD using external encoder to MP3 or FLAC (236466) (Closes: #581598). * Drag and drop from Dolphin doesn't work (242745) (Closes: #600588) * Symbolic links are not added to a project when a folder is added recursively (243555) (Closes: #581070). * Install app icons to hicolor so that they are visible in non KDE WMs (https://bugzilla.novell.com/show_bug.cgi?id=619731) * Translation fixes * Overburn doesn't work (241534) * Data part of mixed CD is not written - searching for previous session doesn't work (246798) * Fixed the speed comparision and formatting when cdrecord changes the writing speed automatically (246262, 243482) (Closes: #608146) Upstream code changes do not seem to be intrusive. Get relevant (without translations) diff with $ debdiff k3b_2.0.0-1.dsc k3b_2.0.1-1.dsc | filterdiff --clean -x *.po -x *.desktop -x *.notifyrc -x *.actions -x *.protocol 2) Closes a significant number of debian bugs (4 bugs + 1 merged). 3) Very good track record in unstable: more than 4 months without regressions [1]. 4) It's a standalone desktop app (its libs have no external rdepends). 5) Some packaging changes could have been avoided but they are not intrusive either. I guess Fathi didn't plan to push it to Squeeze originally. However, I think it would be useful for Squeeze users and this would not hurt release process. Thank you for considering. [1] http://packages.qa.debian.org/k/k3b.html unblock k3b/2.0.1-1 -- System Information: Debian Release: 6.0 APT prefers unstable APT policy: (500, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.36-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=lt_LT.UTF-8, LC_CTYPE=lt_LT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101227220219.6371.31093.report...@mdxdesktop.lan.vainius.eu
Bug#607553: unblock: kdeaccessibility/4:4.4.5-4
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package kdeaccessibility This revision fixes a crash which occurs when new kttsd tries to load an invalid config file which used to be valid in previous versions (lenny). unblock kdeaccessibility/4:4.4.5-4 -- System Information: Debian Release: 6.0 APT prefers unstable APT policy: (500, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.36-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=lt_LT.UTF-8, LC_CTYPE=lt_LT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101219181036.24565.91324.report...@mdxdesktop.lan.vainius.eu
Bug#605883: unblock: a bunch of KDE SC packages
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Hello, I have recently made a series of uploads for fixing issues in KDE SC and I would like to get those package revisions into Squeeze. First of all, thanks for quick unblock of the following: kdebase-workspace/4:4.4.5-5 koffice/1:2.2.1-4 Now remaining packages: * unblock kdenetwork/4:4.4.5-2 This revision fixes an RC bug (#603661) which breaks kopete ICQ support for all users. AOL has recently sold ICQ and, as a result, ICQ main login server address was changed. The fix is trivial: change ICQ server address in kopete to the new one. The patch also includes an standard KDE update script for changing the address in the user config file (if present). The upload also solves circular dependency between kopete and libkopete4. This might ease a job for apt and friends during upgrades (#580044). * unblock kdepimlibs/4:4.4.5-2 While the debian bug is of normal severity (#600907), the issue might have more severe implications. After all it's a crash and memory management bug which typically are a cause of security problems. Anyway, in my opinion, the two-line patch is too trivial to be ignored. * unblock kdeaccessibility/4:4.4.5-2 When I looked at the upstream code of kttsd, I could only bang my head against the wall. Yes, it is that bad and it's beyond me how KDE project could release kttsd in that state to the users. It turns out kttsd 4.3 was just fine but they decided to port it to speech-dispacher. Rather than doing it properly, they only merged a somewhat working KTTS daemon back, commented most of configuration code out and released kttsd 4.4 in this ridiculous state leaving many configuration core and GUI elements not working. Obviously, this is not on par with expectations for Debian stable release and #599825 describes only a small fraction of problems. I considered removing kttsd from archive but it's pretty tightly integrated into KDE and it's pretty important for accessibility purposes. So in 4:4.4.5-2 you see what I had to do to restore KTTS configuration to a usable state. Patches are relatively huge, but they mostly add new or uncomment old GUI related code. Trust me, there is no other way to do this. In hope that my efforts were not wasted, I ask for unblock for this revision. P.S. This leaves Debian Qt/KDE team with two RC bugs (#582953 and #590147) on kdepim which in my opinion date as old as Debian etch. Their real cause is not known and hopes for getting them fixed are low after so many years. What is more, they are rare. -- Modestas Vainius mo...@debian.org signature.asc Description: This is a digitally signed message part.
Bug#605883: unblock: a bunch of KDE SC packages
Hello, On šeštadienis 04 Gruodis 2010 13:47:31 Adam D. Barratt wrote: The changelog seems slightly confused here - some sort of merge artefact? 4:4.1.4-1 has appeared, 4:4.0.68+svn794641-1 has disappeared with its changes re-appearing in 4:4.0.72-1, 4:3.96.0-1 has gained an entry and the stanzas for 4:3.94.0-1 and 4:3.90.1-1 have also vanished. Other than that, the changes themselves look fine; thanks. As with most (all) KDE packages at 4:4.4.5-2, they include changelog clean up. The revisions that were removed from the changelog have never been uploaded to archive and I cleaned/merged them up when migrating packaging VCS to git. Nothing to worry about. * unblock kdepimlibs/4:4.4.5-2 While the debian bug is of normal severity (#600907), the issue might have more severe implications. After all it's a crash and memory management bug which typically are a cause of security problems. Anyway, in my opinion, the two-line patch is too trivial to be ignored. I'm happy with the change here, although this also has changelog rewriting issues. See above. -- Modestas Vainius mo...@debian.org signature.asc Description: This is a digitally signed message part.
Bug#605056: unblock: kde4libs/4:4.4.5-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package kde4libs I have just uploaded a new revision of kde4libs to fix incorrect Replaces with kdelibs-data. This unreported bug could be considered RC. A new revision also includes debian/changelog clean up (for versions which have never been uploaded to archive) and correction of Vcs-* fields, which both are harmless and are a consequence of switching our packaging VCS. unblock kde4libs/4:4.4.5-2 -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.36-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=lt_LT.UTF-8, LC_CTYPE=lt_LT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101126204840.5086.42528.report...@mdxdesktop.lan.vainius.eu
Bug#602302: future unblock: kdepim/4:4.4.7-1
retitle 602302 unblock: kdepim/4:4.4.7-2 thanks Hello, On trečiadienis 03 Lapkritis 2010 17:07:12 Modestas Vainius wrote: Please unblock package kdepim could you consider unblocking kdepim 4.4.7 (4.4.7-1 is experimental) on the same merrits as explained in #596940. 4.4.7 is another bugfix-only release from the kdepim 4.4 stable tree. As agreed with Julien on IRC, I've just uploaded kdepim 4:4.4.7-2 to unstable. Therefore: unblock kdepim/4:4.4.7-2 unblock kdepim-runtime/4:4.4.7-1 -- Modestas Vainius modes...@vainius.eu signature.asc Description: This is a digitally signed message part.
Bug#602302: future unblock: kdepim/4:4.4.7-1
Package: release.debian.org Severity: wishlist User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package kdepim could you consider unblocking kdepim 4.4.7 (4.4.7-1 is experimental) on the same merrits as explained in #596940. 4.4.7 is another bugfix-only release from the kdepim 4.4 stable tree. Unfortunately, the diff is quite noisy because upstream took a hammer approach at fixing probable encoding issues and disabled implicit C++ null-terminated string to Q*String object conversation: --- kdepim-4.4.6/messagecore/CMakeLists.txt 2010-09-10 02:22:43.0 +0300 +++ kdepim-4.4.7/messagecore/CMakeLists.txt 2010-10-22 02:25:03.0 +0300 @@ -1,6 +1,9 @@ set( CMAKE_CXX_FLAGS ${CMAKE_CXX_FLAGS} ${KDE4_ENABLE_EXCEPTIONS} ) add_definitions(-DKDE_DEFAULT_DEBUG_AREA=5300) +add_definitions( -DQT_NO_CAST_FROM_ASCII ) +add_definitions( -DQT_NO_CAST_TO_ASCII ) + add_subdirectory(tests) This obviously broke building so as a result, you see a bunch of changes like this all over the place: -mConfig = new KConfig( kaddressbookrc ); +mConfig = new KConfig( QLatin1String( kaddressbookrc ) ); which are harmless. The interesting part is documented in the changelog. As you see, there are a bunch of crash fixes there: +=== Version 2.4.9 --- 19 October 2010 === +- Fix crash if alarm triggers while its deletion confirmation prompt is visible. +- Fix crash when Try button is clicked while creating new display alarm. +- Fix crash on KAlarm exit. +- Fix possible crash when enabling individual alarms. +- Prevent long file name from expanding the width of file display alarm window. +- Allow pre- post-alarm actions for alarms whose text is generated by a command. +- Combine 4 New Alarm icons in toolbar, to fix icon texts not fitting into width. + which would be useful to have in Squeeze. BTW, there is also kdepim-runtime[2] 4.4.7 in unstable which has no upstream code changes, just a version bump. Unblock it if you choose to unblock kdepim 4.4.7, those two tarballs were released together. unblock kdepim/4:4.4.7-1 [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596940 [2] http://packages.qa.debian.org/k/kdepim-runtime.html -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.36-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=lt_LT.UTF-8, LC_CTYPE=lt_LT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101103150712.6370.44623.report...@mdxdesktop.lan.vainius.eu
Bug#599715: unblock: qimageblitz/1:0.0.6-2
Hello, On penktadienis 22 Spalis 2010 18:53:42 Mehdi Dogguy wrote: On 10/10/2010 14:38, Modestas Vainius wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package qimageblitz Well, frankly there is nothing release important about this update. Regardless if you unblock this package or not, just close this report and I won't bother you again about this topic. But nevertheless it would be great to have 1:0.0.6-2 in squeeze because: I understand your arguments and would have accepted this set of changes during the soft freeze. It just seems late for that now. Besides, the package doesn't fix any RC issue. So… it will stay in unstable for the moment I'm afraid. No problem. -- Modestas Vainius modes...@vainius.eu signature.asc Description: This is a digitally signed message part.
Bug#599715: unblock: qimageblitz/1:0.0.6-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package qimageblitz Well, frankly there is nothing release important about this update. Regardless if you unblock this package or not, just close this report and I won't bother you again about this topic. But nevertheless it would be great to have 1:0.0.6-2 in squeeze because: 1) current qimageblitz package in testing is the same as in lenny. Packaging is rather archaic and uses outdated KDE team packaging practises. It would be great if we didn't have to deal with old cruft for the next 2 years. That's the main reason why this new revision has rather many packaging touches all over the place. But there is nothing ground breaking there; 2) despite upstream version bump, upstream changes are really minimal and basically limited to small build system fixes. There are no changes to symbols and 1:0.0.6-2 has symbol file based on 0.0.4 hence 0.0.6 has no effect on shlibs at all; 3) I had the package ready on 2010-07-28 [1]. But I'd waited for almost two months for upstream to officially release the 0.0.6 tarball which I generated based on their VCS tag. Hence the delay; 4) the package has already spent 20 days in unstable [2]. No new problems were reported. unblock qimageblitz/1:0.0.6-2 [1] http://git.debian.org/?p=pkg-kde/kde-req/qimageblitz.git [2] http://packages.qa.debian.org/q/qimageblitz.html -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.35-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=lt_LT.UTF-8, LC_CTYPE=lt_LT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101010123822.27127.18306.report...@mdxdesktop.lan.vainius.eu
Bug#598436: unblock: konversation/1.3.1-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package konversation This revision adds a patch that fixes (workarounds) a pretty rare but very annoying bug [1] with disappearing cursor. When the bug hits a user, the mouse cursor just disappears once moved over various areas of the application making (parts of) its GUI pretty much unusable. Those parts typically happen to be channel or nick lists. In the former case, it becomes nearly impossible to switch channels with the mouse which is a primary way of doing things in a GUI driven IRC client... What's more, the patch is one-liner. So I see 1.3.1-2 as very good and welcome candidate for squeeze. unblock konversation/1.3.1-2 [1] https://bugs.kde.org/show_bug.cgi?id=217592 -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.35-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=lt_LT.UTF-8, LC_CTYPE=lt_LT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100928220529.17516.52264.report...@mdxdesktop.ozas.sytes.net
Bug#596940: future unblock: kdepim/4:4.4.6-1
Hello, On antradienis 21 Rugsėjis 2010 00:19:10 Mehdi Dogguy wrote: On 09/18/2010 09:19 PM, Modestas Vainius wrote: Hello, On penktadienis 17 Rugsėjis 2010 16:07:23 Mehdi Dogguy wrote: On 15/09/2010 10:55, Modestas Vainius wrote: Speaking strictly about kdepim source package, its diff is rather big (see diffstat below). However, given what I said above, would you grant a freeze exception for this package (after it proves itself in unstable obviously)? Thank you for considering. Having the complete diff would certainly help to decide. Would you mind giving such diff please? (P.S.: You can upload it to experimental if you want) Uploaded as kdepim_4:4.4.6-0exp1 to experimental. There are some changes in the changelog (some entries are removed or modified). Could you tell us why? Ah, that clean up was part of packaging migration to git. All entries which were removed used to represent versions which have never been uploaded to official archive (so they should have never been there in the first place). But I did my best to merge changes into proper entries in order not to lose any authorship information. P.S. You will see such debian/changelog changes in most packages maintained by Debian Qt/KDE team. I cleaned up all packages in such a way. -- Modestas Vainius modes...@vainius.eu signature.asc Description: This is a digitally signed message part.
Bug#596939: future unblock: kdepim-runtime/4:4.4.6-1
Hello, On sekmadienis 19 Rugsėjis 2010 12:55:16 Mehdi Dogguy wrote: On penktadienis 17 Rugsėjis 2010 16:03:47 Mehdi Dogguy wrote: On 15/09/2010 10:55, Modestas Vainius wrote: Would you grant a freeze exception for this package after it spends some time in unstable? Thank you for considering. Yes. Uploaded. The mailed diff didn't contain all the changes… Unblocked. The mail had upstream changes only :) In addition, I fixed RC bug yesterday. -- Modestas Vainius modes...@vainius.eu signature.asc Description: This is a digitally signed message part.
Bug#596939: future unblock: kdepim-runtime/4:4.4.6-1
retitle 596939 unblock: kdepim-runtime/4:4.4.6-1 severity 596939 normal thanks Hello, On penktadienis 17 Rugsėjis 2010 16:03:47 Mehdi Dogguy wrote: On 15/09/2010 10:55, Modestas Vainius wrote: Would you grant a freeze exception for this package after it spends some time in unstable? Thank you for considering. Yes. Uploaded. -- Modestas Vainius modes...@vainius.eu signature.asc Description: This is a digitally signed message part.
Bug#596940: future unblock: kdepim/4:4.4.6-1
Hello, On penktadienis 17 Rugsėjis 2010 16:07:23 Mehdi Dogguy wrote: On 15/09/2010 10:55, Modestas Vainius wrote: Speaking strictly about kdepim source package, its diff is rather big (see diffstat below). However, given what I said above, would you grant a freeze exception for this package (after it proves itself in unstable obviously)? Thank you for considering. Having the complete diff would certainly help to decide. Would you mind giving such diff please? (P.S.: You can upload it to experimental if you want) Uploaded as kdepim_4:4.4.6-0exp1 to experimental. -- Modestas Vainius modes...@vainius.eu signature.asc Description: This is a digitally signed message part.
Bug#596913: unblock: kdeadmin/4:4.4.5-3
reopen 596913 retitle 596913 unblock: kdeadmin/4:4.4.5-4 thanks Hello, On trečiadienis 15 Rugsėjis 2010 08:23:04 Adam D. Barratt wrote: On Wed, 2010-09-15 at 02:27 +0300, Modestas Vainius wrote: Please unblock package kdeadmin new revision fixes RC bug properly and should finally finish python-cupshelpers transition for system-config-printer-kde. Already unblocked by Julien. I had to upload a new revision (4:4.4.5-4) to fix a new RC bug (#597071) and a couple of other usability issues (like enormous window size of system-config- printer-kde). Please unblock this revision too. unblock: kdeadmin/4:4.4.5-4 -- Modestas Vainius modes...@vainius.eu signature.asc Description: This is a digitally signed message part.
Bug#596939: future unblock: kdepim-runtime/4:4.4.6-1
Package: release.debian.org Severity: wishlist User: release.debian@packages.debian.org Usertags: freeze-exception Hello, I would like to hear your opinion before uploading. KDE has recently released a new patch release (4.4.6) for its kdepim suite 4.4.x series (kdepim-runtime and kdepim source packages in Debian). KDE has a rather strict policy what goes into its patch releases (no new features, only bug fixes). So I think it makes much sense to release Squeeze with the latest bugfix version from upstream because a few months of bug fixing went into kdepim* 4.4.6. Also please note that 4.4.6 is probably the last release of the old kdepim* codebase while upstream is actively working on the kdepim* 4.5 which is 70% rewrite so to speak. In my opinion, this makes the update even more important given the length of the Debian stable lifecycle. Speaking strictly about kdepim-runtime source package, the upstream diff is really small (see below). So would you grant a freeze exception for this package after it spends some time in unstable? Thank you for considering. $ diff -uNr kdepim-runtime-4.4.5 kdepim-runtime-4.4.6 | diffstat .krazy|3 --- resources/imap/imapresource.cpp |2 +- resources/imap/settings.cpp |6 -- resources/mailtransport_dummy/Messages.sh |2 +- 4 files changed, 6 insertions(+), 7 deletions(-) $ diff -uNr kdepim-runtime-4.4.5 kdepim-runtime-4.4.6 diff -uNr kdepim-runtime-4.4.5/.krazy kdepim-runtime-4.4.6/.krazy --- kdepim-runtime-4.4.5/.krazy 2009-12-14 12:54:44.0 +0200 +++ kdepim-runtime-4.4.6/.krazy 1970-01-01 03:00:00.0 +0300 @@ -1,3 +0,0 @@ -SKIP /libkdepim-copy/\|/resources/openchange/ -EXTRA defines,kdebug,null,qenums,tipsandthis -STRICT super diff -uNr kdepim-runtime-4.4.5/resources/imap/imapresource.cpp kdepim-runtime-4.4.6/resources/imap/imapresource.cpp --- kdepim-runtime-4.4.5/resources/imap/imapresource.cpp2010-01-06 19:00:55.0 +0200 +++ kdepim-runtime-4.4.6/resources/imap/imapresource.cpp2010-09-10 02:32:13.0 +0300 @@ -256,7 +256,7 @@ if ( userRejected ) { emit status( Broken, i18n( Could not read the password: user rejected wallet access. ) ); return; - } else if ( password.isEmpty() ) { + } else if ( password.isEmpty() (Settings::self()-authentication() != 7 /* Not GSSAPI */) ) { emit status( Broken, i18n( Authentication failed. ) ); return; } else { diff -uNr kdepim-runtime-4.4.5/resources/imap/settings.cpp kdepim-runtime-4.4.6/resources/imap/settings.cpp --- kdepim-runtime-4.4.5/resources/imap/settings.cpp2009-12-14 12:54:43.0 +0200 +++ kdepim-runtime-4.4.6/resources/imap/settings.cpp2010-09-10 02:32:13.0 +0300 @@ -42,6 +42,8 @@ K_GLOBAL_STATIC( SettingsHelper, s_globalSettings ) +static const int s_ModeGSSAPI = 7; + Settings *Settings::self() { if ( !s_globalSettings-q ) { @@ -68,7 +70,7 @@ void Settings::requestPassword() { - if ( !m_password.isEmpty() ) { + if ( !m_password.isEmpty() || ( authentication() == s_ModeGSSAPI ) ) { emit passwordRequestCompleted( m_password, false ); } else { Wallet *wallet = Wallet::openWallet( Wallet::NetworkWallet(), m_winId, Wallet::Asynchronous ); @@ -118,7 +120,7 @@ *userRejected = false; } -if ( !m_password.isEmpty() ) +if ( !m_password.isEmpty() || ( authentication() == s_ModeGSSAPI ) ) return m_password; Wallet* wallet = Wallet::openWallet( Wallet::NetworkWallet(), m_winId ); if ( wallet wallet-isOpen() wallet-hasFolder( imap ) ) { diff -uNr kdepim-runtime-4.4.5/resources/mailtransport_dummy/Messages.sh kdepim-runtime-4.4.6/resources/mailtransport_dummy/Messages.sh --- kdepim-runtime-4.4.5/resources/mailtransport_dummy/Messages.sh 2009-12-14 12:54:44.0 +0200 +++ kdepim-runtime-4.4.6/resources/mailtransport_dummy/Messages.sh 2010-09-10 02:32:16.0 +0300 @@ -1,2 +1,2 @@ #! /usr/bin/env bash -$XGETTEXT *.cpp -o $podir/akonadi_mailtransport_resource.pot +$XGETTEXT *.cpp -o $podir/akonadi_mailtransport_dummy_resource.pot -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.35-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=lt_LT.UTF-8, LC_CTYPE=lt_LT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100915085519.3142.67528.report...@mdxdesktop.ozas.sytes.net
Bug#596940: future unblock: kdepim/4:4.4.6-1
Package: release.debian.org Severity: wishlist User: release.debian@packages.debian.org Usertags: freeze-exception Hello, I would like to hear your opinion before uploading. KDE has recently released a new patch release (4.4.6) for its kdepim suite 4.4.x series (kdepim-runtime and kdepim source packages in Debian). KDE has a rather strict policy what goes into its patch releases (no new features, only bug fixes). So I think it makes much sense to release Squeeze with the latest bugfix version from upstream because a few months of bug fixing went into kdepim* 4.4.6. Also please note that 4.4.6 is probably the last release of the old kdepim* codebase while upstream is actively working on the kdepim* 4.5 which is 70% rewrite so to speak. In my opinion, this makes the update even more important given the length of the Debian stable lifecycle. Speaking strictly about kdepim source package, its diff is rather big (see diffstat below). However, given what I said above, would you grant a freeze exception for this package (after it proves itself in unstable obviously)? Thank you for considering. $ diff -uNr kdepim-4.4.5 kdepim-4.4.6 | diffstat .emacs-dirvars | 14 --- .kateconfig|1 .krazy |5 - blogilo/src/composer/bilboeditor.cpp |2 doc/akregator/index.cache.bz2 |binary doc/blogilo/index.cache.bz2|binary doc/kabcclient/index.cache.bz2 |binary doc/kalarm/index.cache.bz2 |binary doc/kioslave/news/index.cache.bz2 |binary doc/kjots/index.cache.bz2 |binary doc/kleopatra/index.cache.bz2 |binary doc/kmail/index.cache.bz2 |binary doc/knode/index.cache.bz2 |binary doc/knotes/index.cache.bz2 |binary doc/konsolekalendar/index.cache.bz2|binary doc/kontact-admin/index.cache.bz2 |binary doc/kontact/index.cache.bz2|binary doc/korganizer/index.cache.bz2 |binary doc/ktimetracker/index.cache.bz2 |binary doc/kwatchgnupg/index.cache.bz2|binary kalarm/Changelog |9 +- kalarm/alarmcalendar.cpp |9 +- kalarm/cal/kaeventdata.cpp |7 - kalarm/cal/kaeventdata.h | 10 +- kalarm/editdlgtypes.cpp| 18 +++- kalarm/kaevent.h |4 kalarm/kalarm-1.2.1-general.pl | 96 +++ kalarm/kalarm-1.9.5-defaults.pl| 136 - kalarm/kalarm-version.pl | 16 +-- kalarm/kalarm.h|2 kalarm/messagewin.cpp | 10 +- kalarm/prefdlg.cpp |7 + kalarm/sounddlg.cpp| 31 ++- kalarm/sounddlg.h |8 + kalarm/templatedlg.cpp |4 kdepim-version.h |2 kleopatra/crypto/gui/newresultpage.cpp |1 kmail/accountdialog.cpp|8 + kmail/attachmentstrategy.cpp |4 kmail/distributionlistdialog.cpp | 16 +++ kmail/distributionlistdialog.h |2 kmail/folderview.cpp | 13 +-- kmail/headerstyle.cpp |4 kmail/kmaccount.cpp|8 + kmail/kmacctcachedimap.cpp |3 kmail/kmail.kcfg.cmake |6 - kmail/kmailicalifaceimpl.cpp |2 kmail/kmcommands.cpp |8 + kmail/kmcomposewin.cpp |2 kmail/kmfolder.cpp | 14 +-- kmail/kmfolder.h | 10 +- kmail/kmfoldercachedimap.h |2 kmail/kmfolderdialog.cpp |6 + kmail/kmfoldermaildir.cpp | 34 ++-- kmail/kmkernel.cpp | 18 kmail/kmkernel.h |2 kmail/kmmainwidget.h |1 kmail/kmsystemtray.cpp | 20 kmail/mailinglistpropertiesdialog.cpp |4 kmail/mailinglistpropertiesdialog.h|2 kmail/newfolderdialog.cpp |2 kmail/renamejob.cpp| 12 ++ kmail/util.cpp |7 + kmail/util.h |2 knode/knconfigwidgets.cpp |6 + libkdepim/addresseelineedit.cpp|2 mimelib/doc/mimepp.html|2 mimelib/doc/util.html |2 68 files changed, 381 insertions(+), 235 deletions(-) -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.35-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=lt_LT.UTF-8, LC_CTYPE=lt_LT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a
Bug#596912: unblock: kdebindings/4:4.4.5-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package kdebindings new revision contains fixes for the RC and important bug. unblock kdebindings/4:4.4.5-3 -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.35-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=lt_LT.UTF-8, LC_CTYPE=lt_LT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100914232407.31748.24340.report...@mdxdesktop.ozas.sytes.net
Bug#596913: unblock: kdeadmin/4:4.4.5-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package kdeadmin new revision fixes RC bug properly and should finally finish python-cupshelpers transition for system-config-printer-kde. unblock kdeadmin/4:4.4.5-3 -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.35-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=lt_LT.UTF-8, LC_CTYPE=lt_LT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100914232716.32044.68764.report...@mdxdesktop.ozas.sytes.net
Bug#596914: unblock: kdeedu/4:4.4.5-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package kdeedu new revision fixes a bunch of RC bugs (lenny upgrading issues) and a very trivial normal bug (basically a typo). unblock kdeedu/4:4.4.5-2 -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.35-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=lt_LT.UTF-8, LC_CTYPE=lt_LT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100914232931.32140.23866.report...@mdxdesktop.ozas.sytes.net
Bug#596915: unblock: kdepim-runtime/4:4.4.5-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package kdepim-runtime this package used to be covered by auto-freeze exception but it has never migrated to testing due to missing ia64 build. Now I uploaded a manual ia64 build in order to enable 4:4.4.5-1 to migrate. However, random FTBFS on ia64 is still not fixed and is tracked as #596908 now. The bug will be fixed in the next version of the package but I really want to land 4.4.5 to testing beforehand. There is no reason not accept 4:4.4.5-1 as the FTBFS bug is not new and affects current testing version as well. unblock kdepim-runtime/4:4.4.5-1 -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.35-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=lt_LT.UTF-8, LC_CTYPE=lt_LT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100914234052.32412.80028.report...@mdxdesktop.ozas.sytes.net
Bug#579690: transition: KDE SC 4.4.3
Hello, while kdenetwork is not very complicated and fixable (working on it), what can be done about that kdebindings beast? It links the whole distro together (python, mono etc.) so it would be great to see it in testing. Until kdebindings is in, I don't think this bug can be closed. -- Modestas Vainius modes...@vainius.eu signature.asc Description: This is a digitally signed message part.
Bug#579690: transition: KDE SC 4.4.3
Hello, On trečiadienis 12 Gegužė 2010 15:43:43 Adam D. Barratt wrote: kdegames has now built successfully (not least due to your symbols fix); kdeedu, otoh, has been tried on a few buildds and, where it doesn't segfault, fails with (with apologies for any sucky wrapping): cd cantor/src/backends/R /usr/bin/cmake -E cmake_link_script CMakeFiles/cantor_rbackend.dir/link.txt --verbose=1 /usr/bin/g++ -fPIC -g -O2 -g -Wall -O2 -Wnon-virtual-dtor -Wno-long-long -ansi -Wundef -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -Wformat-security -fno-exceptions -DQT_NO_EXCEPTIONS -fno-check-new -fno-common -Woverloaded-virtual -fno-threadsafe-statics -fvisibility=hidden -fvisibility-inlines-hidden -DNDEBUG -DQT_NO_DEBUG -Wl,--enable-new-dtags -Wl,--fatal-warnings -Wl,--no-undefined -lc -Wl,--no-undefined -Wl,--as-needed -shared -Wl,-soname,cantor_rbackend.so -o ../../../../lib/cantor_rbackend.so CMakeFiles/cantor_rbackend.dir/cantor_rbackend_automoc.o CMakeFiles/cantor_rbackend.dir/rbackend.o CMakeFiles/cantor_rbackend.dir/rsession.o CMakeFiles/cantor_rbackend.dir/rexpression.o CMakeFiles/cantor_rbackend.dir/rextensions.o CMakeFiles/cantor_rbackend.dir/settings.o CMakeFiles/cantor_rbackend.dir/rserver_interface.o -L/usr/lib/R/lib -L../../../../lib /usr/lib/libkdeui.so.5.4.0 ../../../../lib/libcantorlibs.so.0.0.1 -lR -lRlapack -lgfortran -lRblas /usr/lib/libQtSvg.so /usr/lib/libQtGui.so /usr/lib/libkdecore.so.5.4.0 /usr/lib/libQtDBus.so /usr/lib/libQtCore.so -Wl,-rpath,/usr/lib/R/lib:/build/buildd-kdeedu_4.4.3-1-armel-hdEaHC/kdeedu- 4.4.3/obj-arm-linux-gnueabi/lib: /usr/bin/ld: cannot find -lgfortran collect2: ld returned 1 exit status Details at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=581237 Yet I'm not going to wait long for it even if the fix in r-base-core would be the most inexpensive way to resolve this FTBFS. If nothing happens today or tomorrow morning, I will try to fix kdeedu (which will be a rather blindly attempt with 50/50 chances of working). -- Modestas Vainius modes...@vainius.eu signature.asc Description: This is a digitally signed message part.
Bug#579690: transition: KDE SC 4.4.3
Hello, On sekmadienis 09 Gegužė 2010 23:06:21 Adam D. Barratt wrote: On Sat, 2010-05-08 at 13:51 +0300, Modestas Vainius wrote: * The following packages failed on all6500-2 and need a give back: kdeaccessibility kdebase kdeedu kdegames Given back. Sigh, all6500-2 claimed kdeedu and kdegames again and (obviously) failed to build them. It also failed plasma-widget-yawp. So these need a give back and all6500-2 blocking again... kdeedu is rather important package which blocks a couple of other ones (kdeplasma-addons, digikam, kphotoalbum). What is more, could you adjust meta-kde aging to 2 or 3 days so KDE starts migrating when the rest of KDE ages normal 10 days? -- Modestas Vainius modes...@vainius.eu signature.asc Description: This is a digitally signed message part.
Bug#579690: transition: KDE SC 4.4.3
Hello, Status update: * all6500-2 buildd seems to have problems building any KDE package (as far I can tell, automoc segfaults randomly there). However, other armel buildds seem to handle KDE packages just fine. So all6500-2 has already been blocked from claiming KDE stuff by my request. I'm CCing ar...@buildd.debian.org so maybe it could determined what is the root cause of these failures. * The following packages failed on all6500-2 and need a give back: kdeaccessibility kdebase kdeedu kdegames * kdemultimedia and kdebindings need maintainer uploads due to FTBFSes on armel and RC bugs. This will be taken care. * kdepim-runtime failed on ia64. However, I successfully built it in developer chroot. So I believe toolchain update in the chroot might fix the issue (from gcc 4.4.3-7 to 4.4.4-1). I sent a mail to i...@buildd.d.o 4 days ago, no reply or action yet. Maybe this could be speeded up a bit. Maintainer action might be needed if give back does not fix the problem. * Third party dependencies have been taken care of. No problems there. -- Modestas Vainius modes...@vainius.eu signature.asc Description: This is a digitally signed message part.
Bug#579690: transition: KDE SC 4.4.3
Hello, On ketvirtadienis 29 Balandis 2010 23:50:19 Modestas Vainius wrote: as a follow up to [1], I open a new bug for KDE SC 4.4.3 transition tracking. Uploads of 20+ KDE SC source packages and a couple of other in-house ones (google-gadgets, libmsn) are currently planned for May 2-4. So as you have probably noticed already, KDE SC 4.4.3 has been uploaded today. I will make -2 uploads of very popular kde4libs and kdepimlibs libraries soon in order to adjust symbol files for weird arches (esp. armel). Although the list is long but actually it affects only the following 3rd party reverse dependencies. Fortunately, all maintainers of these packages are members of pkg-kde so there won't be delays updating the package. Below you will find what needs to be done for third party packages. In the worst case scenario, I could do those uploads myself as a member of KDE Extras Team, but I believe this won't be necessary. Debian KDE Extras Team pkg-kde-ext...@lists.alioth.debian.org digikam Needs maintainer upload, some work has already been done in experimental, bug filled (#579985) http://bugs.debian.org/579985 kipi-plugins Needs maintainer upload, some work already been done in experimental, bug filled (#579984) http://bugs.debian.org/579984 kphotoalbum Needs maintainer upload, bug filled (#579986) http://bugs.debian.org/579986 ktorrent Schedule binNMUs with Dep-Wait on kdebase-workspace-dev (= 4:4.4) Kai Wasserbäch deb...@carbon-project.org plasma-widget-yawp Schedule binNMUs with Dep-Wait on kdebase-workspace-dev (= 4:4.4) I hope I didn't miss anything. -- Modestas Vainius modes...@vainius.eu signature.asc Description: This is a digitally signed message part.
Bug#579690: transition: KDE SC 4.4.3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition User: release.debian@packages.debian.org Usertags: transition Hello, as a follow up to [1], I open a new bug for KDE SC 4.4.3 transition tracking. Uploads of 20+ KDE SC source packages and a couple of other in-house ones (google-gadgets, libmsn) are currently planned for May 2-4. The transition seems to be ready [2] on arches which have functional experimental buildds. FYI, all build failures there have been triggered by bugs of either pkg-kde-tools or attica. Good news is that those bugs have already been fixed in sid. For future reference, please note that starting with 4.4, KDE SC packages include symbol files for all public libraries. This means that packages of new minor upstream releases (e.g. all upstream releases in 4.4 series) will no longer need to migrate to testing together as a whole bunch because intedependences of all KDE SC packages will be tied to the most recent KDE major version (e.g. = 4.4) rather than to the most recent minor one (e.g. = 4.4.{1,2,3}). This means that each source package of KDE SC (whether it includes libraries or not) becomes an independent entity (likely expection being kdebindings) on its own unless we do major packaging changes for minor upstream releases (unlikely) or upload a new major (e.g. from 4.4.x to 4.5.x) upstream release. Therefore, we'll no longer coordinate typical uploads of new minor KDE SC (as entity) upstream releases. Obviously, normal rules still apply and we'll do our best not to upload those individual KDE SC source packages which would negatively impact other ongoing transitions at that moment. Major (e.g. 4.4 - 4.5) upstream upgrades will be coordinated as before because they are always going to be like a shlibs bump in the best case scenario. Yet soname changes, package renames or other major packaging changes are also very likely then. 1. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570360#47 2. https://buildd.debian.org/pkg.cgi?pkg=maint=debian-qt-kde%40lists.debian.orgdist=experimental Below you will find relevant information about the transition most of which has already been posted to bug #570360. -- The following packages will be removed when KDE 4.4 replaces KDE 4.3 currently in sid: kpackage libkonqsidebarplugin4 libkonqsidebarplugin4-dev libkfontinst4 libkwineffects1 libnepomukquery4 libnepomukqueryclient4 libplasma-applet-system-monitor4 libplasmaclock4 libprocesscore4 libprocessui4 libtaskmanager4 libweather-ion4 libsmokeakonadi2 libsmokekde4-2 libsmokeokular2 libsmokeplasma2 libsmokeqimageblitz2 libsmokeqt4-2 libsmokesoprano2 indi libmarble4 kdesnake libkdcraw7 libkdcraw7-dev libkexiv2-7 libkexiv2-7-dev libkipi6 libkipi6-dev kde-i18n-bn kde-i18n-th kde-l10n-bnin kde-l10n-hne kde-l10n-ku kde-l10n-mr kde-l10n-th kpilot libkabcommon4 libkontactinterfaces4 libmaildir4 kdepimlibs-data liblancelot0 kdesdk-dev kdessh kxsldbg Although the list is long but actually it affects only the following 3rd party reverse dependencies. Fortunately, all maintainers of these packages are members of pkg-kde so there won't be delays updating the package. Debian KDE Extras Team pkg-kde-ext...@lists.alioth.debian.org digikam kipi-plugins kphotoalbum ktorrent Kai Wasserbäch deb...@carbon-project.org plasma-widget-yawp In addition, we are going to do google-gadgets and libmsn soname changes. These packages have no dependencies outside KDE (kdebase-workspace and kdenetwork) hence they won't cause any additional trouble. To sum up, KDE SC 4.4 transition will be almost like shlibs bump with a few minor exceptions above. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.33-2-amd64 (SMP w/1 CPU core) Locale: LANG=lt_LT.UTF-8, LC_CTYPE=lt_LT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100429205018.31311.48005.report...@mdxdesktop.ozas.sytes.net
Re: Bug#570360: [release.debian.org]
Hello, Sune Vuorela wrote: It is just a shlibs bump (but with symbol files), and phonon and qt4-x11 sources needs to migrate together. It would be nice to get a binNMU of some packages, like python-qt4 in order to pick up new features (needed for kde4.4), some of these packages is having ifdef'ed code depending on the qt version its built against (the kde 4.4 issues is a bit bigger, but 90% of that is in the kde uploaded source packages) The following packages will be removed when KDE 4.4 is uploaded to sid: kpackage libkonqsidebarplugin4 libkonqsidebarplugin4-dev libkfontinst4 libkwineffects1 libnepomukquery4 libnepomukqueryclient4 libplasma-applet-system-monitor4 libplasmaclock4 libprocesscore4 libprocessui4 libtaskmanager4 libweather-ion4 libsmokeakonadi2 libsmokekde4-2 libsmokeokular2 libsmokeplasma2 libsmokeqimageblitz2 libsmokeqt4-2 libsmokesoprano2 indi libmarble4 kdesnake libkdcraw7 libkdcraw7-dev libkexiv2-7 libkexiv2-7-dev libkipi6 libkipi6-dev kde-i18n-bn kde-i18n-th kde-l10n-bnin kde-l10n-hne kde-l10n-ku kde-l10n-mr kde-l10n-th kpilot libkabcommon4 libkontactinterfaces4 libmaildir4 kdepimlibs-data liblancelot0 kdesdk-dev kdessh kxsldbg Although the list is long but actually it affects only the following 3rd party reverse dependencies. Fortunately, all maintainers of these packages are members of pkg-kde so there won't be delays updating the packages. Debian KDE Extras Team pkg-kde-ext...@lists.alioth.debian.org digikam kipi-plugins kphotoalbum ktorrent Kai Wasserbäch deb...@carbon-project.org plasma-widget-yawp In addition, we are going to do google-gadgets and libmsn soname changes. These packages have no dependencies outside KDE (kdebase-workspace and kdenetwork) hence they won't cause any additional trouble. To sum up, KDE SC 4.4 transition will be almost like shlibs bump with a few minor exceptions above. -- Modestas Vainius modes...@vainius.eu signature.asc Description: This is a digitally signed message part.
Re: the mangling of ‘va_list’ has changed in GCC 4.4
Hello, On ketvirtadienis 28 Sausis 2010 10:23:20 Fathi Boudra wrote: On Wed, Jan 27, 2010 at 11:11 PM, Riku Voipio riku.voi...@iki.fi wrote: Interesting. Do you have a example on howto do that? http://git.debian.org/?p=pkg-kde/qt4-x11.git;a=blob;f=debian/patches/92_arm el_gcc43_valist_compat.diff;h=1db7aa33b73193a8ac0ff563f7a81bff40bfab61;hb=b 3e8073df9201386aa420d5f4cab839615a0c6c5 I have recently came across .symver directive [1][2] that is more straightforward way to achieve the same thing. In that case, only source file (.cpp) needs to be changed. For example: --- $ cat test.h void myprint(const char* fmt, va_list list); $ cat libtest.cpp #include cstdarg #include test.h void myprint(const char* fmt, va_list list) { } // va_list mangling has been changed in g++ 4.4 // Add ABI = g++-4.3 compatibility hack #if defined __ARM_EABI__ defined __GNUC__ (__GNUC__ 4 || __GNUC__ == 4 __GNUC_MINOR__ = 4) __asm__(.symver _Z7myprintPKcSt9__va_list, _Z7myprintPKcPv@@); #endif --- _Z7myprintPKcSt9__va_list ( myprint(char const*, std::__va_list) ) here is the new mangling while _Z7myprintPKcPv ( myprint(char const*, void*) ) is the old mangling. When this code is built under g++-4.4, the resulting binary will have both symbols with _Z7myprintPKcPv and '_Z7myprintPKcSt9__va_list' referring to the same address: $ objdump -T libtest.so | grep _Z7myprint 06d8 gDF .text 0058 Base_Z7myprintPKcSt9__va_list 06d8 gDF .text 0058 Base_Z7myprintPKcPv 1. http://www.redhat.com/docs/manuals/enterprise/RHEL-3-Manual/gnu- assembler/symver.html 2. http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/gnu- linker/version.html -- Modestas Vainius modes...@vainius.eu signature.asc Description: This is a digitally signed message part.
Re: the mangling of ‘va_list’ has changed in GCC 4.4
Hello, On ketvirtadienis 28 Sausis 2010 21:37:15 Riku Voipio wrote: Brilliant! This shall be the plan then: 1) identify affected libraries (Jakubs list as base?) 2) provide patches for the libraries and submit them to BTS 3) give maintainers X days to MU the libraries, after that proceed to NMU them 4) binNMU any packages using the functions with va_list parameters 5) release squeeze ;) 6) tell maintainers they are free to drop the symbol alias 1. Step 4 is optional and can be skipped. 2. WRT step 6, I don't think it is correct. Maintainer may only drop the alias when changing the name of the affected library package (most likely due to soname change). This step is not related to squeeze release. -- Modestas Vainius modes...@vainius.eu signature.asc Description: This is a digitally signed message part.
Bug#560802: pu: package amarok/1.4.10-2lenny1
Hello, On sekmadienis 13 Gruodis 2009 19:33:01 Adam D. Barratt wrote: Hi, On Sat, 2009-12-12 at 13:55 +0200, Modestas Vainius wrote: several users have been bugging me to fix #512847 [1]. Current amarok version in lenny does not display anything in the Wikipedia tab because wikipedia has changed its site layout a bit since 1.4.10 release. The patch to fix this problem is extremely trivial so I think it's worth a stable update to make a group of users happy. Debdiff below. Please go ahead. Uploaded source+all+amd64. -- Modestas Vainius modes...@vainius.eu signature.asc Description: This is a digitally signed message part.
Bug#560802: pu: package amarok/1.4.10-2lenny1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: pu Hello, several users have been bugging me to fix #512847 [1]. Current amarok version in lenny does not display anything in the Wikipedia tab because wikipedia has changed its site layout a bit since 1.4.10 release. The patch to fix this problem is extremely trivial so I think it's worth a stable update to make a group of users happy. Debdiff below. 1. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=512847 diff -u amarok-1.4.10/debian/changelog amarok-1.4.10/debian/changelog --- amarok-1.4.10/debian/changelog +++ amarok-1.4.10/debian/changelog @@ -1,3 +1,9 @@ +amarok (1.4.10-2lenny1) stable; urgency=low + + * Fix Wikipedia tab (patch 22_fix_wikipedia_tab.diff) (Closes: #512847). + + -- Modestas Vainius modes...@vainius.eu Sat, 12 Dec 2009 13:19:45 +0200 + amarok (1.4.10-2) unstable; urgency=high * Add 20_security_audible_tags.diff patch to fix integer overflow while diff -u amarok-1.4.10/debian/patches/series amarok-1.4.10/debian/patches/series --- amarok-1.4.10/debian/patches/series +++ amarok-1.4.10/debian/patches/series @@ -17,2 +17,3 @@ 20_security_audible_tags.diff +22_fix_wikipedia_tab.diff 97_automake_cleanup.diff only in patch2: unchanged: --- amarok-1.4.10.orig/debian/patches/22_fix_wikipedia_tab.diff +++ amarok-1.4.10/debian/patches/22_fix_wikipedia_tab.diff @@ -0,0 +1,11 @@ +--- a/amarok/src/contextbrowser.cpp b/amarok/src/contextbrowser.cpp +@@ -4189,7 +4189,7 @@ + } + + // Ok lets remove the top and bottom parts of the page +-m_wiki = m_wiki.mid( m_wiki.find( h1 class=\firstHeading\ ) ); ++m_wiki = m_wiki.mid( m_wiki.find( h1 id=\firstHeading\ ) ); + m_wiki = m_wiki.mid( 0, m_wiki.find( div class=\printfooter\ ) ); + // Adding back license information + m_wiki += copyright; -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: libgps18 - libgps19 transition
Hello, On trečiadienis 09 Gruodis 2009 22:53:21 Luk Claes wrote: Bernd Zeimetz wrote: Luk Claes wrote: Bernd Zeimetz wrote: Hi Release-Team, with the next upload of gpsd to unstable we'll have a transition from libgps18 to libgps19. As KDE is involved, I'm CCing the QT/KDE list also. Whats the best time for an upload? As long as it does not interfere with the gstreamer0.10 transition (which I doubt it does) it should be fine. It should not mess with gstreamer related packages. Uploaded to unstable a few seconds ago, please schedule binNMUs with a dep-wait on libgps-dev = 2.90-2 Scheduled. kdebase-workspace and kdeedu 4:4.3.2 (currently in archive) will FTBFS. This will fixed in 4:4.3.4-1 of both (coming soon). -- Modestas Vainius modes...@vainius.eu signature.asc Description: This is a digitally signed message part.
Re: Hinting amarok/taglib-extras/taglib to testing?
Hello, could somebody look at amarok / taglib-extras / taglib migration to testing? Unless I'm missing something, they are all ready, but still stuck for some reason and, unfortunately, [1] does not make much sense. Probably, britney is confused about Breaks: libtag-extras0 I added to libtag1c2a and can't figure out what to do. Any ideas? Because I don't want to do any sourceful upload to fix this in order not to catch Qt 4.5.3 / KDE 4.3.2 or similar sid-only dep. -- Modestas Vainius modes...@vainius.eu signature.asc Description: This is a digitally signed message part.
Hinting amarok/taglib-extras/taglib to testing?
Hello, could somebody look at amarok / taglib-extras / taglib migration to testing? Unless I'm missing something, they are all ready, but still stuck for some reason and, unfortunately, [1] does not make much sense. Probably, britney is confused about Breaks: libtag-extras0 I added to libtag1c2a and can't figure out what to do. 1. http://release.debian.org/migration/testing.pl?package=amarok -- Modestas Vainius modes...@vainius.eu signature.asc Description: This is a digitally signed message part.
Re: libmtp7 - libmtp8 transition
Hello, 2009 m. February 21 d., Saturday, Adeodato Simó rašė: * amarok The version currently in experimental (2.0.1.1-1) depends already on libmtp8. Nothing to do here. Such version of Amarok depends on KDE4, and I don't think it'll be uploaded to unstable in time for the libmtp transition. Can you look into whether the unstable version of amarok (1.4.10-2) can be built against libmtp8 as-is, or with some minor patch? Thanks. libmtp is going to be the least of amarok 1 problems. It is going to face removal of KDE 3 desktop from unstable and libgpod transition soon. This means it is going to need much work. I'm not saying it is not possible to do (ubuntu has done it and most work could be stolen from them), but given that: 1) Amarok 1 is _dead_ upstream, it is thing of the past and definitely not what final squeeze is going to have. 2) I'm no _longer interested_ in Amarok 1 at all hence I don't want to invest time in it. I'm currently heading towards asking for its temporal removal (until amarok 2) from testing (to unblock other transitions) rather than fixing the package. However, this letter should not be considered as removal request just yet. Amarok 2 is a big pain too since it currently depends on quite many experimental packages: KDE4, libmtp, debhelper and, most importantly, mysql- server-5.1. What is more, Amarok 2 works only on i386/amd64 at the moment (due to mysql-server-5.1 / MySQL embedded deficiencies). So don't worry, I'll resolve amarok mess myself one way or another. -- Modestas Vainius modes...@vainius.eu signature.asc Description: This is a digitally signed message part.
Please unblock and give back amarok 1.4.10-2
Hello, please unblock amarok 1.4.10-2. It fixes security issue. please giveback amarok on arm (to the faster buildd) as previous attempt failed with the typical shlibdeps timeout. -- Modestas Vainius modes...@vainius.eu signature.asc Description: This is a digitally signed message part.
Re: Bug#500540: Unblock suggestion: kdebase
Hello, ketvirtadienis 11 Gruodis 2008, Asheesh Laroia rašė: If debian-release *really* would prefer a 4:3.5.9.dfsg.1-5+lenny1 that only fixes the RC and removes the other two changes, I can work on preparing it. It doesn't seem a productive use of time but I leave that decision to debian-release. kdebase is not a problem [1], b0rked jack-audio-connection-kit [2] on alpha is the problem. I strongly believe that 4:3.5.9.dfsg.1-6 could be unlocked as is if jack wasn't blocking it. 1. http://buildd.debian.org/pkg.cgi?pkg=kdebase 2. http://buildd.debian.org/pkg.cgi?pkg=jack-audio-connection-kit -- Modestas Vainius modes...@vainius.eu signature.asc Description: This is a digitally signed message part.
Please unblock ktorrent2.2, please consider ktorrent
Hello, 1) Upstream released a new upstream version of ktorrent2.2 _solely_ for the purpose of fixing 2 security problems (#504178). It is in sid (2.2.8). Please unblock it. 2) A clone of those security bugs (#503817) is still open for ktorrent/lenny. A new upstream release (which upstream considers bugfix one, _no new features_) of ktorrent in sid has at least 4-5 crash fixes, a fix for 100% CPU bug (#502071), 2 security fixes (#503817), a memory leak fix, a fix for torrent/HTTP protocol violation. In three months that 3.1.2, 3.1.3 and 3.1.4 have spent in unstable no new bugs have been reported against them in Debian which wouldn't affect 3.1.1 either (i.e. there are no known regressions). Personally, I would be very disappointed as a maintainer and as a user if Lenny was released with 3.1.1. But whether you're going to trust me on this one and even if you don't how much potential harm a bugfix update of a completely standalone application could do are up to you to decide. Upstream Changelog below: -- Changes in 3.1.4 : - Make sure user is properly logged in when handling a torrent post in the webgui - Prevent PHP injection attacks in webgui - Update file size in CacheFile::growFile, this fixes a SIGBUS error (172814) - Fix bug causing infinite DNS lookups in UDP tracker when lookup fails - Remove default label text KSqueezedTextLabel in trackerview (173065) Changes in 3.1.3 : - Make login into webinterface secure - Check if menus are created properly before showing them - Stop KT from exiting when scanfolder loads a plugin silently and KT is hidden in systray. - Make sure duplicate URL's are not shown in trackerview - Fix problem causing file priorities not to be read at startup - Make sure added.f is filled in with the proper flags for each peer in the added field of a PEX message (169014) - Make sure it is not required to put http:// for the proxy in the config dialog (169133) - Fix typo in advanced pref - Fix bug causing webseed not to download last chunk of a request - Fix bug which resulted in speeds of webseed not getting calculated - Fix rename of groups when edit is not initialized via context menu - Make toolbars hideable - Make sure that files can not be moved to the location they are already in - Don't start torrents at startup when a torrent is user controlled and over limit - Fix crash in logging code due to 0 pointer - Remove bitoogle from default search engine list Changes in 3.1.2 : - Improved performance of GUI updates - Make sure app icon is set (mostly for windows) - Fix crash when clicking on clear search history button twice (167580) - Backported some improvements to download thread - Make sure cookies are not sent in http announces - Fix crash at startup which started happening since KDE 4.1 - Fix problem causing massive memory usage (148385) - Fix issue causing Timer class to stop working when day changes - Make sure toolbar settings are restored properly - Fix compile error on arm architecture - Fixed some bugs in file deselection code -- Modestas Vainius [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part.
Re: Re: Freeze exception request: kde4libs 4.1.0-3
Hello, khtml: Debian: kparts;kjs;kio;kdeui;kdecore Upstream: kparts;kjs;kio;kdeui;kdecore Proposed: kparts;kio;kdeui;kdecore kjs is private library. Public kjsapi links against it. kfile: Debian: kio;kdeui;kdecore Proposed: ${QT_QTCORE_LIBRARY};${QT_QTGUI_LIBRARY};kio;kdeui kdecore is implicit (pulled in recursively by kdeui). kross/ui: Debian: krosscore Proposed: ${QT_QTGUI_LIBRARY};kparts Nothing links against kross in archive now. And addition of new libraries is harmless. ++if(WIN32) ++ set(kdecore_LINK_INTERFACE_LIBRARIES ${QT_QTDBUS_LIBRARY};${QT_QTCORE_LIBRARY};${KDEWIN32_LIBRARIES}) ++else(WiN32) else(..) statement is probably considered a part of the command which is case insensitive. kdelibs would not build if the typo was harmful. Btw, it is in the original source, not debian patches (4.1.0-1 has it). -- Modestas Vainius [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part.
Re: [Pkg-kde-extras] Amarok: SECURITY ISSUE in Debian Etch and Lenny
Hi, antradienis 19 rugpjūtis 2008, Neil McGovern rašė: What about: src/scripts/rbot/* rbot is an internal amarok IRC bot (or something similar). See src/scripts/rbot/README. It has never been installed to the user system (see src/scripts/Makefile.am in 1.4.9.1) doc/ru/* Not sure about this. Maybe this translation was found out to be too fuzzy. Anyway, it was upstream decision and it is just a translation. -- Modestas Vainius [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part.
Give back amarok on armmips
Hello, please give back amarok on arm mips. Both failures were buildd problems [1]. 1. http://buildd.debian.org/~jeroen/status/package.php?suite=unstablep=amarok -- Modestas Vainius [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part.
Please retry qt-x11-free 3.3.8b-2 on alpha mips
Hello, It would be great if you could retry qt-x11-free 3.3.8b-2 builds on alpha and mips. Previous builds failed due to non obvious reasons[1] which don't seem to be architecture specific (unless I'm missing something). 1. http://buildd.debian.org/pkg.cgi?pkg=qt-x11-free -- Modestas Vainius [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part.
Re: Please retry qt-x11-free 3.3.8b-2 on alpha mips
Hi, 2008 m. February 20 d., Wednesday, Riku Voipio rašė: I think it would be better to fix qt-x11-free not to fail to build randomly? Well, qt-x11-free 3.3.8b-2, which is supposed to end qt3 built with -O0 life cycle in Debian, migration to testing is part of the bigger plan. qt-x11-free 3.3.8b-3 will be built with optimizations (-O2) and will lose over 5700 inline debug symbols (which, as we expect [1], do not matter). So 3.3.8b-3 should enter unstable ASAP to see if transition is really not needed. 3.3.8b-2 in testing will stay as safety fallback for users in case of problems with -3. 1. http://lists.debian.org/debian-release/2008/02/msg00232.html -- Modestas Vainius [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part.
Re: Proposal(s) for handling libqt3-mt situation
Hi, 2008 m. February 16 d., Saturday, Pierre Habouzit rašė: Okay that's quite a few, so the Conflict option sucks. Here is another plan, tell me what you think, we put a debian specific hack in the glibc to reenable the extern inlines for _ONLY_ the packages that ask for it, for lenny, and remove it in lenny+1. Ok, so it's actually a debate whether to readd missing symbols to affected libraries themselves or to libc6-dev. If Matthew is correct, all packages except trustedqsl are victims of libqt3-mt. By the way, I'm not sure if tsql is a problem (atoi is versioned?): $ objdump -tT /usr/bin/tqsl | grep atoi DF *UND* 0015 GLIBC_2.2.5 atoi $ objdump -tT /usr/bin/tqslcert | grep atoi DF *UND* 0015 GLIBC_2.2.5 atoi $ objdump -Tt /usr/lib/libtqsllib.so.1.0.0 | grep atoi DF *UND* 0015 GLIBC_2.2.5 atoi Qt _has_ to use it to build, though digikam and friends won't, so that they will _stop_ using the damn symbols. This way partial upgrades to lenny works, and in lenny+1 the symbols just disappear for good. Sorry, but that's wrong. It's true that Qt gets those symbols at compile time, but any binaries linking against Qt references [fl]?stat64 from Qt at link time. Hence as long any application using [fl]?stat64 are linked against Qt3 with [fl]?stat64 exported (and that has nothing to do with headers), it will depend on [fl]?stat64 being present. If what you say was true, ktorrent 2.2.5.dfsg.1-1 should not depend on fstat64, because 1. ktorrent 2.2.5.dfsg.1-1 was uploaded on Wed, 06 Feb 2008 23:07:08 +0200, hence built against libc6-dev (= 2.7) without extern inlines in sys/stat.h That's essentially the same as it would be building without -D_USE_DEBIAN_GLIBC_EXTERN_INLINE_HACK 2. qt-x11-free 3.3.7-9 was uploaded on Wed, 26 Sep 2007 21:42:24 +0200, hence built against libc6-dev ( 2.7) with extern inlines in sys/stat.h present. That's essentially the same as it would be building with -D_USE_DEBIAN_GLIBC_EXTERN_INLINE_HACK 3. ktorrent 2.2.5.dfsg.1-1 was linked against qt-x11-free 3.3.7-9 (app, not using -D_USE_DEBIAN_GLIBC_EXTERN_INLINE_HACK, was linked against lib, using -D_USE_DEBIAN_GLIBC_EXTERN_INLINE_HACK). As you see, all conditions were met, but, unfortunately, ktorrent 2.2.5.dfsg.1-1 still depends on exported fstat64 No Conflicts are needed, We only need a list of _library_ packages that have the stat (and other symbols) defined reuploaded with a -D_USE_DEBIAN_GLIBC_EXTERN_INLINE_HACK in the CFLAGS. Do you want to add hack to lib6-dev just for Qt3? Then a binNMU campaign of the broken _packages_ has to follow (digikam, k3b, ... ) so that they loose their wrong *UND* symbols for good. Unless libqt3-mt loses them, binNMUs won't help. P.S. However, we might want to delay libqt3-mt transition (by adding back [fl]?stat64 symbols one way or another and forgetting it) to lenny+1, because it's very likely that there will have been fewer applications using it by then. -- Modestas Vainius [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part.