Bug#590147: Repost here test case for akregator
All I really did was rephrase the akregator issue in terms of the upstream dump command. If you look at the upstream tarball for metakit, it builds a binary (command) called dump. If you run it against one of the metakit database files from http://www.file-upload.net/download-2910539/Archive_old.tar.gz.html , you will find that it segfaults. -- Asheesh. -- 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/alpine.deb.2.00.1102170745560.1...@rose.makesad.us
Bug#613827: okular: Okular does not support custom page numbers (such as roman numerals or a page number offset)
Package: okular Version: 4:4.4.5-2 Severity: wishlist This refers to Bug 187237 of the KDE bugtracking system. The 'custom page number' feature is very useful in Adobe Reader since many documents have 'logical page 1' that is different from the 'physical page 1' in the file. Of course, in the TOC everything refers to logical pages, so it would be great to be able to have these in Okular's page display, too. Just look at how Adobe is doing it... -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages okular depends on: ii kdebase-runtime 4:4.4.5-1runtime components from the offici ii libc6 2.11.2-11Embedded GNU C Library: Shared lib ii libfreetype62.4.2-2.1FreeType 2 font engine, shared lib ii libjpeg62 6b1-1The Independent JPEG Group's JPEG ii libkdecore5 4:4.4.5-3the KDE Platform Core Library ii libkdeui5 4:4.4.5-3the KDE Platform User Interface Li ii libkio5 4:4.4.5-3the Network-enabled File Managemen ii libkparts4 4:4.4.5-3the Framework for the KDE Platform ii libkpty44:4.4.5-3the Pseudo Terminal Library for th ii libkutils4 4:4.4.5-3various utility classes for the KD ii libokularcore1 4:4.4.5-2libraries for the Okular document ii libphonon4 4:4.6.0really4.4.2-1 the core library of the Phonon mul ii libpoppler-qt4-30.12.4-1.2 PDF rendering library (Qt 4 based ii libqca2 2.0.2-1 libraries for the Qt Cryptographic ii libqimageblitz4 1:0.0.6-2QImageBlitz image effects library ii libqt4-dbus 4:4.6.3-4Qt 4 D-Bus module ii libqt4-svg 4:4.6.3-4Qt 4 SVG module ii libqt4-xml 4:4.6.3-4Qt 4 XML module ii libqtcore4 4:4.6.3-4Qt 4 core module ii libqtgui4 4:4.6.3-4Qt 4 GUI module ii libspectre1 0.2.6-1 Library for rendering PostScript d ii libstdc++6 4.4.5-6 The GNU Standard C++ Library v3 ii phonon 4:4.6.0really4.4.2-1 metapackage for the Phonon multime ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime okular recommends no packages. Versions of packages okular suggests: ii ghostscript8.71~dfsg2-10 The GPL Ghostscript PostScript/PDF pn kttsd none(no description available) pn okular-extra-backends none(no description available) pn poppler-data none(no description available) ii texlive-binaries 2009-7Binaries for TeX Live ii unrar 1:4.0.3-1 Unarchiver for .rar files (non-fre -- 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/20110217135934.15558.67673.reportbug@Sandbank.localhost
Processed: Re: Bug#613827: okular: Okular does not support custom page numbers (such as roman numerals or a page number offset)
Processing commands for cont...@bugs.debian.org: tags 613827 upstream Bug #613827 [okular] okular: Okular does not support custom page numbers (such as roman numerals or a page number offset) Added tag(s) upstream. thanks Stopping processing here. Please contact me if you need assistance. -- 613827: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613827 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.1297960411432.transcr...@bugs.debian.org
Bug#613827: okular: Okular does not support custom page numbers (such as roman numerals or a page number offset)
tags 613827 upstream thanks Hello, the bug you reported is a KDE bug. Debian Qt/KDE maintainers do not have resources to deal with non Debian-specific bugs and therefore it is unlikely that your bug will be solved if you do not report it to KDE developers directly (unless it is/has been reported by somebody else). Whenever you open a bug report on the KDE bug tracking system, or you find that the bug has been already reported on it, you can couple both this Debian bug and the KDE bug together by sending the mail with the text below to cont...@bugs.debian.org (replace KDE-BUG-URL with the address of the bug report on https://bugs.kde.org/) Do not heasitate in contacting me if you need further assistance. [ copy this ] forwarded 613827 KDE-BUG-URL thanks [ copy this ] Thank you, -- Quote me as saying I was mis-quoted. -- Groucho Marx Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Processed: [bts-link] source package kdepim
Processing commands for cont...@bugs.debian.org: # # bts-link upstream status pull for source package kdepim # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). # remote status report for #525045 (http://bugs.debian.org/525045) # * http://bugs.kde.org/show_bug.cgi?id=188902 # * remote status changed: UNCONFIRMED - RESOLVED # * remote resolution changed: (?) - FIXED # * closed upstream tags 525045 + fixed-upstream Bug #525045 [korganizer] korganizer: weekly and daily view is broken Added tag(s) fixed-upstream. usertags 525045 - status-UNCONFIRMED Bug#525045: korganizer: weekly and daily view is broken Usertags were: status-UNCONFIRMED. Usertags are now: . usertags 525045 + status-RESOLVED resolution-FIXED Bug#525045: korganizer: weekly and daily view is broken There were no usertags set. Usertags are now: status-RESOLVED resolution-FIXED. # remote status report for #613371 (http://bugs.debian.org/613371) # * http://bugs.kde.org/show_bug.cgi?id=266297 # * remote status changed: (?) - UNCONFIRMED usertags 613371 + status-UNCONFIRMED Bug#613371: [kmail] Does not attach with command line using relative path There were no usertags set. Usertags are now: status-UNCONFIRMED. thanks Stopping processing here. Please contact me if you need assistance. -- 613371: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613371 525045: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=525045 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.12979605881924.transcr...@bugs.debian.org
[bts-link] source package kdepim
# # bts-link upstream status pull for source package kdepim # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #525045 (http://bugs.debian.org/525045) # * http://bugs.kde.org/show_bug.cgi?id=188902 # * remote status changed: UNCONFIRMED - RESOLVED # * remote resolution changed: (?) - FIXED # * closed upstream tags 525045 + fixed-upstream usertags 525045 - status-UNCONFIRMED usertags 525045 + status-RESOLVED resolution-FIXED # remote status report for #613371 (http://bugs.debian.org/613371) # * http://bugs.kde.org/show_bug.cgi?id=266297 # * remote status changed: (?) - UNCONFIRMED usertags 613371 + status-UNCONFIRMED thanks -- 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/20110217163628.21597.71931.btsl...@busoni.debian.org
Lauris pofigaa tirgo revolveri!
Mangalu tirgus placii sodien var dabuut revolveri Kimber Aegis Nav nepiecieshama ne papiirus, ne atlauju no policista! Neparproti, un mekle konkretaja rajonaa: http://www.nelegalaspistoles.info ! -- 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/20110217175755.968fe2d0...@sun.esstel.ru
Bug#613866: RM: klamav -- ROM; - KDE3 package with no KDE4 port planned
Package: ftp.debian.org Severity: normal Debian qt/kde team plans removal of Qt3/KDE3 for Wheezy and klamav upstream does not plan to port to KDE4, so we may as well go ahead and remove this now. -- 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/20110217203756.10179.96151.reportbug@localhost6.localdomain6
RFC: bringing back task packages
A long time ago, tasksel installed task packages, which were regular metapackages. This was dropped because the task packages had to Depend on many packages, which made the installed system brittle, and made testing propigation a problem. Now that Recommends are installed by default, I'm revisiting the idea of using task packages. It solves many issues and inconsistencies with tasksel vs the rest of Debian. The other problem with task packages before is that tasksel allowed the user to select from amoung all that were available, and this resulted in a confusing long mess of tasks to choose from. To avoid that, I intend to keep the ultimate decision about what tasks are displayed in tasksel under the control of the tasksel maintainers. But, I do hope that moving more of the maintenance of tasks to the developers responsible for those areas of Debian will result in a better selection of software and less work. We've already had some good progress in that area with the gnome metapackages which are used by tasksel. If tasksel was switched to task packages, the task packages would probably be initially built from tasksel's source. They could be split out of tasksel's source as other groups stepped up to maintain them. ## Questions for teams ### gnome Would the gnome team want to maintain a task-gnome? Much of tasksel's gnome task is already taken from the gnome-core and gnome metapackages, with a few more things added. task-gnome would not need to deal with core X desktop stuff; task-desktop would still handle that. Although we could move away from having a task-desktop if you'd prefer. There are also many localized desktop tasks. Mostly these add things like localization packages for openoffice, and occasionally some fonts. I'd like to see those be maintained in conjunction with task-gnome, but it would mean some coordination with the dozens of people who currently maintain those localization tasks. ### kde, lxde, xfce See above and s/gnome/$you/ ### cups Would the cups maintainers be interested in maintaining a task-print-server? Keeping the right ppds and cups packages in the task has been an ongoing issue for me. Note that a subset of cups is also installed as part of the desktop tasks, and it would also make sense to have a metapackage on the cups side that desktop tasks could use. The sole different currently is that openprinting-ppds is included in the print server task, but not the desktop tasks. ### blends I think there is interest in getting some blends displayed in Taskel? It's mostly orthagonal to this proposal, but this would help with giving you full control over what your tasks do. I do feel that blends need to be listed below the other tasks in tasksel, and probably with a divider between them. Also, we have been careful to only have ten tasks, to avoid overloading the user; and there is a limit to the length of the list before it begins scrolling, so the d-i team would have to look at the UI before adding Blends to the interface. ### i18n There are many language tasks in tasksel. It might be good to have the task packages be moved out of tasksel; I don't know if it'd make sense to have individual language teams maintain them, or what. If tasksel displayed Task packages' short Description fields, those would need to be translated. I know we have translated Descriptions but I don't know about coverage, or if that info is available when tasksel runs in d-i? ## Comparing tasksel and dpkg fields Key - Depends This would be an improvement, as new Depends of a task would be installed on upgrade; there is currently no way to upgrade a task and get new packages that have been added to it. Note that Britney already treats Key as Depends internally. So this change would not impact testing migration. Packages - Recommends Recommends may be better than what we have now in tasksel. If aptitude auto-selects *new* recommends of a previously installed package to be installed? Currently new Packages added to a task only affect new installations of that task. Most packages in a task need to be Recommends, to avoid wedging Britney, and to allow removing bits of a task that are not wanted. Note that the Task field on the package side, which is added to the archive based on data from tasksel, could go away. Enhances - ??? The Enhances fields are not truely the same as Depends (but are probably closer to Depends than to dpkg's Enhances). A task that Enhances other tasks is hidden, and auto-force-installed when the other tasks are installed. Relevance - ??? This is used to do some UI ordering of tasks. Closest equivilant is Priority, but it's not granular enough. Test- - ??? These fields specify programs to run to test if the task should be force-auto-installed, or hidden, or selected for installation. Description
