Re: A Debian sprint for package management GUIs?
[ adding -sprints in the loop ]
On Thu, Nov 24, 2011 at 12:01:38AM +0100, Josselin Mouette wrote:
given the poor state of our desktop package management tools in squeeze,
and the number of unknown variables when it comes to wheezy, I’d like to
propose to gather around in a dedicated Debian sprint on this topic. We
should be able to get funding from the project for such a task.
Schedule could include:
* Upstream and Debian state of synaptic, update-*, aptdaemon,
software-center, PackageKit and related packages
* What features we want to expose on our desktop environments (use
cases, interaction scenarios)
* Which tools to focus on to provide these features for wheezy
* Trying to envision what features we want in wheezy+1 and how to
make this happen
* Initial common hacking session to get wheezy on the right tracks
How many of you would be interested in such a meeting?
I answer mainly with DPL hat on: I'll be happy to sponsor such a sprint.
See http://wiki.debian.org/Sprints for info, including friendly venues
we're in touch with (but feel free to propose new ones that better suit
your needs!).
Cheers.
--
Stefano Zacchiroli zack@{upsilon.cc,pps.jussieu.fr,debian.org} . o .
Maître de conférences .. http://upsilon.cc/zack .. . . o
Debian Project Leader... @zack on identi.ca ...o o o
« the first rule of tautology club is the first rule of tautology club »
signature.asc
Description: Digital signature
Re: A Debian sprint for package management GUIs?
Am Donnerstag, den 24.11.2011, 00:01 +0100 schrieb Josselin Mouette: Hi, given the poor state of our desktop package management tools in squeeze, and the number of unknown variables when it comes to wheezy, I’d like to propose to gather around in a dedicated Debian sprint on this topic. We should be able to get funding from the project for such a task. Hello Josselin, Sounds like a good idea. I would like to take part in such a meeting - depending on my available time (I am working in shifts). Michael, Julian and me already already started preparing updates to the software-center/aptdaemon stack. The hardcoded Canonical parts in software-center have been made optionally. As posted by Michael Canonical offers to host ratings and reviews for Debian packages. The server side is under AGPL3 but requires a launchpad account to make a comment or rating [1]. Would need some investigation if this can be hosted on a Debian server with a more general OAuth authentication. At the AppStream sprint in spring OCS open collaboration services [1] was chosen as the target API for the non-Canonical software-center ratings and review system. But the server side doesn't look very good currently: midgard2 doesn't support the PHP middleware yet. Working opensocial implementation can be found at formeego [3] or at opendesktop [4]. Furthermore aptdaemon now also provides the PackageKit system D-Bus interface by reusing the old PackageKit apt backend and mapping aptdaemon transactions. You can already use gpk-application and gpk-update-viewer with aptdaemon. [5] So you will very likely see a wider adoption of the PackageKit api in Ubuntu. Gnome-codec-installer was replaced by session-installer in Ubuntu now since session-installer was ported to GTK3 and provides some unique features like handling of only partially provided codecs and promoting the codecs which are supported best. Cheers, Sebastian [1] http://reviews.ubuntu.com [2] http://socialdesktop.org/ocs/ [3] http://apps.formeego.org/applications/ [4] http://www.opendesktop.org [5] http://lists.freedesktop.org/archives/packagekit/2011-November/006456.html -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1322126352.20787.29.camel@klapprechner
Bug#649687: plasma-desktop dies
You mean I have to ask the user to erase everything in $HOME to make sure that plasma-desktop doesn't die? Sorry, but this doesn't answer the question. How can I set ulimit -c unlimited before plasma-desktop is run to make sure that there is a core dump for investigation? Regards Harri -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ece0ee1.2060...@aixigo.de
Bug#649687: plasma-desktop dies
On Thursday, 2011-11-24, Harald Dunkel wrote: You mean I have to ask the user to erase everything in $HOME to make sure that plasma-desktop doesn't die? Sorry, but this doesn't answer the question. How can I set ulimit -c unlimited before plasma-desktop is run to make sure that there is a core dump for investigation? You could restart plasma-desktop manually on a shell kquitapp plasma-desktop ulimit -c unlimited plasma-desktop Has the additional advantage that you could redirect its text output to file(s). Cheers, Kevin signature.asc Description: This is a digitally signed message part.
Re: A Debian sprint for package management GUIs?
On Thu, Nov 24, 2011 at 12:01:38AM +0100, Josselin Mouette wrote: Hi, given the poor state of our desktop package management tools in squeeze, and the number of unknown variables when it comes to wheezy, I’d like to propose to gather around in a dedicated Debian sprint on this topic. We should be able to get funding from the project for such a task. The state of GNOME/GTK+ package management in squeeze was the same as in Ubuntu's LTS version. For wheezy, the only question is whether we want to go with the Ubuntu stack again, or go with PackageKit on our own. On the KDE side, things do not look that good AFAICT. They have an update notifier, but AFAIK not much more than that; and apparently not enough people to do more. They could go with QApt/Muon or with PackageKit, whatever they choose. Schedule could include: * Upstream and Debian state of synaptic, update-*, aptdaemon, software-center, PackageKit and related packages From what I know, all packages except for update-notifier are actively developed. * What features we want to expose on our desktop environments (use cases, interaction scenarios) * Which tools to focus on to provide these features for wheezy * Trying to envision what features we want in wheezy+1 and how to make this happen * Initial common hacking session to get wheezy on the right tracks How many of you would be interested in such a meeting? Theoretically yes, practically no, at least not before the middle of February. I'm in my first semester at university now, and in general not very travel-friendly (especially if it means travelling outside of Hesse). -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. pgpZJxQaeomQW.pgp Description: PGP signature
Re: A Debian sprint for package management GUIs?
Hi! I would also be interested in this meeting, especially in the PackageKit side. I believe PK is the right way to go, but only if the current APTcc backend gets a few improvements and if we identify the (Debian-specific) stuff PK is probably missing. On KDE's side, I hope I can find a sponsor for Apper soon, so this software management UI is available on Debian too. So Debian/KDE can choose between Apper and Muon there. On Debian/GNOME I think the most user-friendly alternative is the Ubuntu Software Center at time, although there are CLA issues. An alternative would be waiting for GNOME-PackageKit to get application-installer support, but this will probably take some time, since Richard Hughes has lots of stuff to do... But the GPK Update-Viewer is a very nice application with great GNOME integration, so maybe it makes sense to use parts of GPK. In any case we need to think about AppStream and probably communicate things with other distributors (what is the current state of AppStream?) - although focusing on Debian is definitely required. If this meeting takes place in Cologne, I'll definitely come if I don't have tests in that week. (I'm only ~30min away from Cologne) It's great that this thing is discussed! Cheers, Matthias 2011/11/24 Julian Andres Klode j...@debian.org: On Thu, Nov 24, 2011 at 12:01:38AM +0100, Josselin Mouette wrote: Hi, given the poor state of our desktop package management tools in squeeze, and the number of unknown variables when it comes to wheezy, I’d like to propose to gather around in a dedicated Debian sprint on this topic. We should be able to get funding from the project for such a task. The state of GNOME/GTK+ package management in squeeze was the same as in Ubuntu's LTS version. For wheezy, the only question is whether we want to go with the Ubuntu stack again, or go with PackageKit on our own. On the KDE side, things do not look that good AFAICT. They have an update notifier, but AFAIK not much more than that; and apparently not enough people to do more. They could go with QApt/Muon or with PackageKit, whatever they choose. Schedule could include: * Upstream and Debian state of synaptic, update-*, aptdaemon, software-center, PackageKit and related packages From what I know, all packages except for update-notifier are actively developed. * What features we want to expose on our desktop environments (use cases, interaction scenarios) * Which tools to focus on to provide these features for wheezy * Trying to envision what features we want in wheezy+1 and how to make this happen * Initial common hacking session to get wheezy on the right tracks How many of you would be interested in such a meeting? Theoretically yes, practically no, at least not before the middle of February. I'm in my first semester at university now, and in general not very travel-friendly (especially if it means travelling outside of Hesse). -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAKNHny9+LJKs2URGigQmxXgDMX6qESZ=8yNrRFOZGuG==sl...@mail.gmail.com
Bug#649687: plasma-desktop dies
On 11/24/11 15:01, Harald Dunkel wrote: You mean I have to ask the user to erase everything in $HOME to make sure that plasma-desktop doesn't die? Sorry, but this doesn't answer the question. How can I set ulimit -c unlimited before plasma-desktop is run to make sure that there is a core dump for investigation? Regards Harri This way we could see what was causing the problem, is it user specific setting or something else. -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ece6a9e.5010...@gmail.com
Bug#649899: libdbusmenu-qt2: Source URL and author of one package patch are wrong
Package: libdbusmenu-qt2 Version: 0.9.0-0ubuntu2 Severity: minor I just merged the latest unreleased version of libdbusmenu-qt package and noticed too minor errors: - debian/copyright: Source should be https://launchpad.net/libdbusmenu-qt - debian/002-use-multiarch-lib-paths.diff: Author should be Aurélien Gâteau aurelien.gat...@ubuntu.com -- System Information: Debian Release: wheezy/sid APT prefers oneiric-updates APT policy: (500, 'oneiric-updates'), (500, 'oneiric-security'), (500, 'oneiric'), (400, 'oneiric-proposed'), (100, 'oneiric-backports') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-12-generic (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libdbusmenu-qt2 depends on: ii libc6 2.13-20ubuntu5 Embedded GNU C Library: Shared lib ii libgcc1 1:4.6.1-9ubuntu3 GCC support library ii libqt4-dbus 4:4.7.4-0ubuntu8 Qt 4 D-Bus module ii libqtcore4 4:4.7.4-0ubuntu8 Qt 4 core module ii libqtgui4 4:4.7.4-0ubuntu8 Qt 4 GUI module ii libstdc++6 4.6.1-9ubuntu3 GNU Standard C++ Library v3 ii multiarch-support 2.13-20ubuntu5 Transitional package to ensure mul libdbusmenu-qt2 recommends no packages. libdbusmenu-qt2 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2024170243.18430.8318.reportbug@trinity
Bug#649917: missing file
Package: kdegames usr/share/kde4/apps/kdegames/pics/star.png is not installed in kdegames. In ubuntu i've put it into libkdegames5a.install -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2024191328.gw9...@starsky.19inch.net
Bug#649918: kded_networkstatus.so segfaulting with ntrack 016-1
Package: kdebase-runtime Version: 4:4.6.5-1+b1 Following an upgrade of libntrack-qt4-1 and libntrack0 to version 016-1, kded4 segfaults on startup with the following backtrace: Application: KDE Daemon (kded4), signal: Segmentation fault [KCrash Handler] #6 0x7f50dbae8337 in ?? () from /usr/lib/libntrack.so.0 #7 0x7f50dbae8bae in ntrack_monitor_get () from /usr/lib/libntrack.so.0 #8 0x7f50dbcf0041 in QNtrack::QNtrack() () from /usr/lib/libntrack-qt4.so.1 #9 0x7f50dbcf0125 in QNtrack::instance() () from /usr/lib/libntrack-qt4.so.1 #10 0x7f50dbef91de in NtrackNetworkState::NtrackNetworkState (this=0x9350f0, statusmodule=0x936dd0) at ../../../solid-networkstatus/kded/ntracknetworkstate.cpp:57 #11 0x7f50dbef7df8 in NetworkStatusModule::NetworkStatusModule (this=0x936dd0, parent=optimized out) at ../../../solid-networkstatus/kded/networkstatus.cpp:80 #12 0x7f50dbef8937 in KPluginFactory::createInstanceNetworkStatusModule, QObject (parentWidget=optimized out, parent=optimized out, args=...) at /usr/include/kpluginfactory.h:473 #13 0x7f50eacc34b1 in KPluginFactory::create (this=0x903900, iface=0x7f50ead12d00 KDEDModule, parentWidget=0x0, parent=0x80cf20, args=..., keyword=optimized out) at ../../kdecore/util/kpluginfactory.cpp:203 #14 0x7f50ec9a0804 in createKDEDModule (args=..., parent=0x80cf20, this=optimized out) at ../../kdecore/util/kpluginfactory.h:503 #15 Kded::loadModule (this=0x80cf20, s=..., onDemand=true) at ../../kded/kded.cpp:410 #16 0x7f50ec9a1098 in Kded::loadModule (this=0x80cf20, obj=..., onDemand=true) at ../../kded/kded.cpp:362 #17 0x7f50ec9a1324 in Kded::messageFilter (message=optimized out) at ../../kded/kded.cpp:205 #18 0x7f50ea841ce5 in QDBusConnectionPrivate::handleMessage (this=0x7f9a60, amsg=...) at qdbusintegrator.cpp:552 #19 0x7f50ea845b65 in qDBusSignalFilter (connection=optimized out, message=optimized out, data=0x7f9a60) at qdbusintegrator.cpp:541 #20 0x7f50e6602276 in dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #21 0x7f50ea839029 in q_dbus_connection_dispatch (connection=optimized out) at qdbus_symbols_p.h:115 #22 QDBusConnectionPrivate::doDispatch (this=0x7f9a60) at qdbusintegrator.cpp:1124 #23 0x7f50ea87c084 in QDBusConnectionPrivate::qt_metacall (this=0x7f9a60, _c=QMetaObject::InvokeMetaMethod, _id=optimized out, _a=0x801860) at .moc/release-shared/moc_qdbusconnection_p.cpp:98 #24 0x7f50ea4fe6ca in QObject::event (this=0x7f9a60, e=optimized out) at kernel/qobject.cpp:1217 #25 0x7f50eb1839f4 in notify_helper (e=0x8013a0, receiver=0x7f9a60, this=0x80e150) at kernel/qapplication.cpp:4467 #26 QApplicationPrivate::notify_helper (this=0x80e150, receiver=0x7f9a60, e=0x8013a0) at kernel/qapplication.cpp:4439 #27 0x7f50eb11 in QApplication::notify (this=0x7fffa631d310, receiver=0x7f9a60, e=0x8013a0) at kernel/qapplication.cpp:4346 #28 0x7f50ebeb0b96 in KApplication::notify (this=0x7fffa631d310, receiver=0x7f9a60, event=0x8013a0) at ../../kdeui/kernel/kapplication.cpp:311 #29 0x7f50ea4e7fbc in QCoreApplication::notifyInternal (this=0x7fffa631d310, receiver=0x7f9a60, event=0x8013a0) at kernel/qcoreapplication.cpp:731 #30 0x7f50ea4eb378 in sendEvent (event=0x8013a0, receiver=0x7f9a60) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #31 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x7db590) at kernel/qcoreapplication.cpp:1372 #32 0x7f50ea512663 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220 #33 postEventSourceDispatch (s=optimized out) at kernel/qeventdispatcher_glib.cpp:277 #34 0x7f50e7dfb4a3 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #35 0x7f50e7dfbc80 in ?? () from /lib/libglib-2.0.so.0 #36 0x7f50e7dfbf1d in g_main_context_iteration () from /lib/libglib-2.0.so.0 #37 0x7f50ea512abf in QEventDispatcherGlib::processEvents (this=0x80e0e0, flags=optimized out) at kernel/qeventdispatcher_glib.cpp:422 #38 0x7f50eb2279ce in QGuiEventDispatcherGlib::processEvents (this=optimized out, flags=optimized out) at kernel/qguieventdispatcher_glib.cpp:204 #39 0x7f50ea4e71c2 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #40 0x7f50ea4e73bf in QEventLoop::exec (this=0x7fffa631d2a0, flags=...) at kernel/qeventloop.cpp:201 #41 0x7f50ea4eb567 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1008 #42 0x7f50ec9a01f5 in kdemain (argc=1, argv=0x7fffa631d6e8) at ../../kded/kded.cpp:925 #43 0x7f50ec631ead in __libc_start_main (main=optimized out, argc=optimized out, ubp_av=optimized out, init=optimized out, fini=optimized out, rtld_fini=optimized out, stack_end=0x7fffa631d6d8) at libc-start.c:228 #44 0x004006e1 in _start () kded4 starts successfully if I move /usr/lib/kde4/kded_networkstatus.so out of the way to prevent kded4 from
Processed: Re: Bug#649259: frescobaldi fails to start when libpython2.6 is not installed
Processing commands for cont...@bugs.debian.org: clone 649259 -1 Bug#649259: frescobaldi fails to start when libpython2.6 is not installed Bug 649259 cloned as bug 649936. reassign -1 python-kde4 4:4.6.80-3 Bug #649936 [frescobaldi] frescobaldi fails to start when libpython2.6 is not installed Bug reassigned from package 'frescobaldi' to 'python-kde4'. Bug No longer marked as found in versions frescobaldi/1.2.0-1. Bug #649936 [python-kde4] frescobaldi fails to start when libpython2.6 is not installed Bug Marked as found in versions pykde4/4:4.6.80-3. retitle -1 python-kde4: Python modules linked with libpython Bug #649936 [python-kde4] frescobaldi fails to start when libpython2.6 is not installed Changed Bug title to 'python-kde4: Python modules linked with libpython' from 'frescobaldi fails to start when libpython2.6 is not installed' severity 649259 serious Bug #649259 [frescobaldi] frescobaldi fails to start when libpython2.6 is not installed Severity set to 'serious' from 'normal' retitle 649259 frescobaldi: should use default version of Python Bug #649259 [frescobaldi] frescobaldi fails to start when libpython2.6 is not installed Changed Bug title to 'frescobaldi: should use default version of Python' from 'frescobaldi fails to start when libpython2.6 is not installed' user debian-pyt...@lists.debian.org Setting user to debian-pyt...@lists.debian.org (was jw...@debian.org). usertags 649259 + python2.7 python2.6-removal Bug#649259: frescobaldi: should use default version of Python There were no usertags set. Usertags are now: python2.7 python2.6-removal. thanks Stopping processing here. Please contact me if you need assistance. -- 649259: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649259 649936: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649936 -1: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=-1 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.132217207812914.transcr...@bugs.debian.org
Bug#649963: kdeplasma-addons-dbg depends on obsolete package
Package: kdeplasma-addons kdeplasma-addons-dbg depends on kdebase-workspace-dbg in Git packaging, it should depend on kde-workspace-dbg Jonathan -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2025014904.ge9...@starsky.19inch.net
