Bug#894476: #894476: Solved from the Qt side. (rcc: please honour SOURCE_DATE_EPOCH)

[Thomas Preud'homme]

On jeudi 12 juillet 2018 18:28:21 BST Sune Vuorela wrote:
> On Wednesday, July 11, 2018 10:08:23 PM CEST Vagrant Cascadian wrote:
> > Ideally QT_RCC_SOURCE_DATE_OVERRIDE would get set based on
> > SOURCE_DATE_EPOCH, otherwise build tools have an arbitrary growing
> 
> No. As explained, we need to look at each individual package to check if the
> timestamp is actually used for anything. It can be. It probably is.
> 
> I think a better fix might be to specifically mark in the rcc file if the
> dates are important or not. But it requires involvement upstream. (Or maybe
> if the rcc file is autogenerated or not). I don't think it is a problem for
> non- autogenerated rcc files.

Agreed, it's only a problem for files autogenerated at build time. rcc on a 
file that's part of the source tarball is gonna give a reproducible result.

Best regards,

Thomas

signature.asc
Description: This is a digitally signed message part.

Bug#894476: RCC: provide option to encode EPOCH timestamp

[Thomas Preud'homme]

On April 3, 2018 10:15:42 PM GMT+01:00, "Lisandro Damián Nicanor Pérez Meyer" 
 wrote:
>El mar., 3 de abr. de 2018 16:42, Sune Vuorela 
>escribió:
>
>> On Tuesday, April 3, 2018 9:24:58 PM CEST Chris Lamb wrote:
>> > I'm not /entirely/ sure what the difference is as I'm not in the
>> > Qt/RCC world too often these days (alas !), but why just not use
>> > SOURCE_DATE_EPOCH *iff* it is exported?
>> >
>> > Normal systems simply do not have this envvar set, so there is
>really
>> > no danger of it leaking elsewhere or causing unintended
>side-effects.
>>
>> We don't know how application users are using this.
>>
>> The following is some theoretical example, that I'm quite sure could
>be
>> used
>> in some real world applications:
>>
>> QFileInfo embeddedFile(":/foo/data.xml"); // fallback downloaded in
>the
>> ancient past
>> QFileInfo systemfile("/usr/share/foo/data.xml");
>>
>> if (systemfile.lastModified() > embeddedFile.lastModified())
>> {
>>data = readFromFile(systemFile);
>> }
>> else
>> {
>>data = readFromFile(embeddedFile);
>> }
>>
>> If S_D_E gets used, rather than the data.xml modified date in the
>source,
>> this
>> will end up using the wrong file if S_D_E is newer than the system
>copy of
>> the
>> file.
>>
>> This is not a unused databit, but a fully available piece of metadata
>for
>> the
>> files.
>
>
>I'm afraid Sune is right here, it might be used that way. Questionable?
>Sure thing, but still valid code.
>
>But after all the same can be said from embedding translations into the
>binary itself.
>
>So yes, we will need help from upstream with this one.
>
>>
>>

Maybe the solution is then not in rcc but in whatever generate the files that 
the qrc that rcc processes refer to. For instance in the case of ultracopier 
lrelease could have a mean if generating .qm files with the same modified 
timestamp as the .ts file it processes. This would guarantee stable output for 
a stable source and this later on rcc would also generate stable output.

Thoughts?

Best regards,

Thomas

Bug#894476: RCC: provide option to encode EPOCH timestamp

[Thomas Preud'homme]

On April 3, 2018 8:20:22 PM GMT+01:00, Sune Vuorela  wrote:
>On Tuesday, April 3, 2018 9:14:23 PM CEST Chris Lamb wrote:
>> Hi Sune!
>> 
>> > I don't think honouring SOURCE_DATE_EPOCH is the right idea under
>normal
>> > circumstances
>> 
>> Can you elaborate on what you mean by "normal circumstances"? :)
>
>"normal circumstances" is rcc on a source file, as opposed to an
>autogenerated 
>file.
>
>> How about e use S_D_E if it is setup/exported, otherwise use the
>mtime
>> of the file as before?
>
>I think that using S_D_E only makes sense if rcc is run on an
>autogenerated 
>file, but I do think that most rcc runs is run on existing source
>files.
>
>
>I don't have a good idea to differentiate those.
>
>/Sune
>-- 
>I didn’t stop pretending when I became an adult, it’s just that when I
>was a 
>kid I was pretending that I fit into the rules and structures of this
>world. 
>And now that I’m an adult, I pretend that those rules and structures
>exist.
>   - zefrank

One small clarification: in my case rcc *is* run on a nongenerated resource 
file. It's some of the files that the resource file list that are generated and 
whose timestamp end up in the cpp file generated by rcc.

In other hand:

foo.qrc mentions bar.qm which is generated from bar.ts.

rcc foo.qrc generates resource_bar.cpp which contains constant data that 
encodes bar.qm timestamp and this create different resource_bar.o at every 
build.

Best regards,

Thomas

Bug#894476: RCC: provide option to encode EPOCH timestamp

[Thomas Preud'homme]

On April 3, 2018 7:25:03 PM GMT+01:00, Sune Vuorela  wrote:
>On Saturday, March 31, 2018 12:05:02 PM CEST Chris Lamb wrote:
>> > While investigating ultracopier's lack of build reproducibility, I
>found
>> > out that rcc encodes the timestamp of the files the QRC file being
>> > compiled references
>
>I don't actually see why this should be a problem. If input changes,
>output 
>changes.
>I do think that using touch(1) on the input should allow different
>output.
>
>It is quite easy to reproduce:
>
>qtbase/tests/auto/gui/image/qimage/foo (dev $%=)$ rcc --format-version
>2 ../
>qimage.qrc -o 1
>qtbase/tests/auto/gui/image/qimage/foo (dev $%=)$ rcc --format-version
>2 ../
>qimage.qrc -o 2
>qtbase/tests/auto/gui/image/qimage/foo (dev $%=)$ rcc --format-version
>2 ../
>qimage.qrc -o 3
>
>Gives same output.
>Even adding in touch ../qimage.qrc keeps the same output.
>
>qtbase/tests/auto/gui/image/qimage/foo (dev $%=)$ rcc --format-version
>2 ../
>qimage.qrc -o 4
>
>touch ../images/image.bmp
>
>qtbase/tests/auto/gui/image/qimage/foo (dev $%=)$ rcc --format-version
>2 ../
>qimage.qrc -o 5
>
>is needed to get different output
>
>14ef6dae8e4992ce907948c1c4af272b  1
>14ef6dae8e4992ce907948c1c4af272b  2
>14ef6dae8e4992ce907948c1c4af272b  3
>14ef6dae8e4992ce907948c1c4af272b  4
>54c6f8c09a347955ae2f36e68bbd2539  5
>
>
>So. What touches the files?
>
>/Sune
>-- 
>I didn’t stop pretending when I became an adult, it’s just that when I
>was a 
>kid I was pretending that I fit into the rules and structures of this
>world. 
>And now that I’m an adult, I pretend that those rules and structures
>exist.
>   - zefrank

Hi Sune,

The problematic files are Qt message files (ie .qm files) generated at build 
time via lrelease from translation files (ie .ts files). Therefore two 
different builds will generate those .qm files at different times which will 
end up with different cpp files generated by rcc. Currently I'm working around 
it by setting the modified time of those .qm files to EPOCH after they are 
generated. I think it would be nice if there was a way for rcc to avoid doing 
that manually. I agree with Chris that honouring SOURCE_DATE_EPOCH in rcc would 
be a nice solution.

Best regards,

Thomas

Bug#894476: RCC: provide option to encode EPOCH timestamp

[Thomas Preud'homme]

Package: qtbase5-dev-tools
Version: 5.9.2+dfsg-12
Severity: wishlist
Tags: upstream
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps toolchain

Hi,

While investigating ultracopier's lack of build reproducibility, I found
out that rcc encodes the timestamp of the files the QRC file being
compiled references (see end of RCCFileInfo::writeDataInfo()). This
becomes a problem for generated files because the output of rcc is then
different in 2 different builds. It would be nice if rcc had an option
to encode a stable timestamp, eg. EPOCH.

Best regards,

Thomas

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (900, 'unstable'), (500, 'unstable-debug'), (500, 
'stable-updates'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.15.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR:fr (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages qtbase5-dev-tools depends on:
ii  libc62.27-2
ii  libgcc1  1:8-20180321-1
ii  libqt5core5a [qtbase-abi-5-9-2]  5.9.2+dfsg-12
ii  libqt5dbus5  5.9.2+dfsg-12
ii  libstdc++6   8-20180321-1
ii  perl 5.26.1-5
ii  qtchooser64-ga1b6736-5
ii  zlib1g   1:1.2.8.dfsg-5

qtbase5-dev-tools recommends no packages.

qtbase5-dev-tools suggests no packages.

-- no debconf information

Bug#882833:

[Thomas Preud'homme]

Changing ServerPath in ~/.config/akonadi/akonadiserverrc to /usr/sbin/mysqld-
akonadi solved the issue for me. Maybe this should be updated automatically 
somehow?

Best regards,

Thomas

signature.asc
Description: This is a digitally signed message part.

Bug#882833: (no subject)

[Thomas Preud'homme]

I've also had issues with kontact and my .xsession-errors contained the 
following lines:

org.kde.pim.akonadiserver: database server stopped unexpectedly 

org.kde.pim.akonadiserver: stderr: "mysqld: [ERROR] Could not open required 
defaults file: 
$HOME/.local/share/akonadi/mysql.conf\nmysqld: [ERROR] Fatal error in defaults 
hand


Where $HOME and $USER are substitution of my own to mask my home directory and 
username.

I've noticed some DENIED lines in dmesg that seem related:

audit: type=1400 audit(1515103889.923:49): apparmor="DENIED" operation="open" 
profile="/
usr/sbin/mysqld" name="$HOME/.local/share/akonadi/mysql.conf" pid=2655 
comm="mysqld" requested_mask="r" denied_mask="r" fsuid=1000 

== Successful attempt ==


Trying to launch the mysqld command mentioned in .xsession-errors but using 
mysqld-
akonadi instead (which seems to have special treatment for 
$HOME/.local/share/akonadi) 
and relaunching akonadi and then kontact seems to have worked (am writing this 
from that 
very kontact process).

Best regards,

Thomas


signature.asc
Description: This is a digitally signed message part.

Bug#794110: plasma-workspace: plasmashell segmentation fault (11) every few minutes (and restarted)

[Thomas Preud'homme]

On vendredi 16 juin 2017 19:04:54 BST Sven-Haegar Koch wrote:
> On Fri, 16 Jun 2017, Maximiliano Curia wrote:
> > Control: tag -1 + unreproducible
> > 
> > El 2016-04-14 a las 13:12 -0300, Lisandro Damián Nicanor Pérez Meyer 
escribió:
> > > We expect this might get fixed with Qt 5.6, and we are waiting for 5.6.1
> > > to
> > > be released to push it to unstable.
> > 
> > We are currently using qt 5.7.1 for stretch, and I haven't seen this issue
> > in a while now. Is any one still able to reproduce this issue?
> 
> For me this also did not happen anymore for quite some time, at least
> over a year ago.

Likewise, I did not experience such a crash for quite a while now.

Best regards,

Thomas

signature.asc
Description: This is a digitally signed message part.

Bug#794110: More info needed

[Thomas Preud'homme]

Le mercredi 16 mars 2016, 10:16:18 Lisandro Damián Nicanor Pérez Meyer a écrit 
:
> tag 794110 moreinfo
> thanks
> 
> Hi everyone! With my Qt maintainer hat on, I would like you to give me some
> info.
> 
> First: We have only one backtrace coming from the original submitter. Can
> the rest of you check if when a crash happens the current thread's (the
> crashing one) backtrace says something like:

Hi Lisandro,

I hope you are doing well.

Sorry for the late answer, I was in the middle of a relocation and didn't 
touch my computer much. I haven't had any crash since I have so the bug seems 
to be solved on my side. I'll update the bug report if I ever get a new crash 
in the following (14) days but I don't expect to.

Best regards,

Thomas

signature.asc
Description: This is a digitally signed message part.

Bug#794110: Related to #797862?

[Thomas Preud'homme]

I also experience this bug. However I noticed that after some time I
will have several plasmashell running, one of them taking 100% of the
CPU it's running on. It thus seems this bug triggers in return #797862.

Best regards,


signature.asc
Description: PGP signature

Bug#805175: libkonq-common: konqpopupmenuplugin not working on KDE SC 5

[Thomas Preud'homme]

Package: libkonq-common
Version: 4:15.08.2-1
Severity: normal
Tags: upstream

Hi,

There is no action entries (such as to compress/decompress) in the right
click menu on KDE SC 5 due to konqpopupmenuplugin.desktop missing in
/usr/share/kservicetypes5. I know this was fixed upstream [1] but not
part of any release yet. This can be worked around though by providing a
symbolic link from
/usr/share/kde4/servicetypes/konqpopupmenuplugin.desktop to
/usr/share/kservicetypes5/

Since the first file is provided by this package, maybe the symlink
could be provided here too until the upstream bug fix flows to a Debian
package.

[1] https://bugs.kde.org/show_bug.cgi?id=350769

Best regards.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (900, 'unstable'), (500, 'stable-updates'), (500, 'testing'), 
(500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages libkonq-common depends on:
ii  libc6   2.19-22
ii  libkdecore5 4:4.14.13-1
ii  libkio5 4:4.14.13-1
ii  libkonq5-templates  4:15.08.2-1
ii  libphonon4  4:4.8.3-2
ii  libqt4-dbus 4:4.8.7+dfsg-3
ii  libqtcore4  4:4.8.7+dfsg-3
ii  libqtgui4   4:4.8.7+dfsg-3
ii  libstdc++6  5.2.1-23
ii  phonon  4:4.8.3-2

libkonq-common recommends no packages.

libkonq-common suggests no packages.

-- no debconf information

Re: Bug#713885: im-config: Sourcing of 20_ibus.rc fails when shell is zsh

[Thomas Preud'homme]

Control: reassign -1 kdm
Control: retitle -1 kdm does not execute Xsession scripts as sh scripts

Currently, when the user shell is zsh, kdm launch the X session in zsh 
emulation mode (it does emulate -R zsh in /etc/kde4/kdm/Xsession). However, 
all X session scripts assume bourne shell behavior. In particular, this leads 
to a bug in /usr/share/im-config/data/20_ibus.rc

This file contains several line like this one:

for IM_CONFIG_MARKER in $(ls /usr/lib/*/gtk-2.0/*/immodules/im-ibus.so \
/usr/lib/gtk-2.0/*/immodules/im-ibus.so 2/dev/null || 
true); do

In zsh emulation mode this fails because either all the modules are in arch-
specific path, or not and in this case zsh just returns an error. Quoting 
zshexpn manpage:

The word is replaced with a list of sorted filenames that match the pattern. If 
no matching pattern is found, the shell gives an error message, unless the 
NULL_GLOB option is set, in  which  case  the  word is deleted; or unless the 
NOMATCH option is unset, in which case the word is left unchanged.

Because of this, GTK and QT apps don't use ibus despite it being running.

I tried changing the emulate -R zsh line by emulate -R sh and it now works 
great for me since more than a week. It seems though that kdm developers 
explicitely want the shell to behave in its normal mode since you run set +o 
posix for bash so there might be a reason to execute zsh in zsh emulation 
mode.

Therefore, I'm not sure what the correct solution is but Osamu Aoki, 
maintainer of im-config, believe that Xsession scripts should be executed in 
bourne shell mode as can be seen from the few #!/bin/sh shebang lines in 
/etc/X11/Xsession and in some other places (I forgot where).

Best regards,

Thomas


signature.asc
Description: This is a digitally signed message part.

Bug#671379: kate: Can't input dead keys in search box

[Thomas Preud'homme]

Package: kate
Version: 4:4.7.4-2
Severity: normal

Dear Maintainer,

I can't enter dead keys in the search box of both kwrite, kate and kile.
For instance, if I create a new file in kwrite and try a search, it
won't let me input ê or even ^ (done by pressing the ^ and then space).

Interestingly, if I copy paste such a letter it works and then the
problem disappear until I reopen the file.

Best regards.

Thomas Preud'homme

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'stable-updates'), (500, 'testing'), 
(500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-2-amd64 (SMP w/4 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 kate depends on:
ii  kate-data   4:4.7.4-2
ii  katepart4:4.7.4-2
ii  kde-runtime 4:4.7.4-2
ii  libc6   2.13-32
ii  libkateinterfaces4  4:4.7.4-2
ii  libkdecore5 4:4.7.4-4
ii  libkdeui5   4:4.7.4-4
ii  libkfile4   4:4.7.4-4
ii  libkio5 4:4.7.4-4
ii  libknewstuff2-4 4:4.7.4-4
ii  libknewstuff3-4 4:4.7.4-4
ii  libkparts4  4:4.7.4-4
ii  libktexteditor4 4:4.7.4-4
ii  libplasma3  4:4.7.4-4
ii  libqt4-dbus 4:4.8.1-1
ii  libqt4-qt3support   4:4.8.1-1
ii  libqt4-sql  4:4.8.1-1
ii  libqt4-xml  4:4.8.1-1
ii  libqtcore4  4:4.8.1-1
ii  libqtgui4   4:4.8.1-1
ii  libstdc++6  4.7.0-7

kate recommends no packages.

Versions of packages kate suggests:
ii  aspell0.60.7~20110707-1
ii  khelpcenter4  4:4.7.4-2
ii  konsole   4:4.7.4-2

-- 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/20120503162646.11033.18461.report...@cerclon.rsr.lip6.fr

Bug#570409: kate: Sometime bad placement of cursor if writing at end of line with static word wrap

[Thomas Preud'homme]

Package: kate
Version: 4:4.3.4-1
Severity: normal

With static word wrap activated, if you try to write at the beginning of a word
which is at end of line, when the word is finally moved to the next line, the
cursor is moved at the end of the word. This is wrong because there is no
reason that the edition that was performed at the beginning of the word is
finished. Bug could be related to bug #481291

Here is how you can reproduce the bug:

- activate static word wrap at 80 columns
- Write the following line : thing thing thing thing thing thing thing thing 
thing thing thing thing thing thing
  (the last thing should be moved on the next line because of insufficient
  space)
- Move the cursor at the beginning of the last thing of the first line, after
  the last space
- Try to add a thing  by just writing it
- You should now have : thinthingg  thing on the second line, with the cursor
  between the two space after thinthingg

What is expected is at least:
thing thing thing thing thing thing thing thing thing thing thing thing
thing thing thing

with the cursor after the first space on the second line.

Or better:

thing thing thing thing thing thing thing thing thing thing thing thing thing
thing thing

with cursor at the beginning of the second line. But this require to test,
after hitting the space, that the new word can fit on the previous line
(since when the word was written it was considering as the beginning of
the next word since there wasn't any space yet and was too long to fit
on the first line whatever the size of the new word is small enough).

Hope I'm clear enough

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-trunk-686 (SMP w/1 CPU core)
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 kate depends on:
ii  kdebase-runtime   4:4.3.4-2  runtime components from the offici
ii  kdelibs5  4:4.3.4-1  core libraries for all KDE 4 appli
ii  libc6 2.10.2-5   Embedded GNU C Library: Shared lib
ii  libplasma34:4.3.4-1  library for the KDE 4 Plasma deskt
ii  libqt4-dbus   4:4.5.3-4  Qt 4 D-Bus module
ii  libqt4-qt3support 4:4.5.3-4  Qt 3 compatibility library for Qt 
ii  libqt4-xml4:4.5.3-4  Qt 4 XML module
ii  libqtcore44:4.5.3-4  Qt 4 core module
ii  libqtgui4 4:4.5.3-4  Qt 4 GUI module
ii  libstdc++64.4.3-2The GNU Standard C++ Library v3

kate recommends no packages.

Versions of packages kate suggests:
ii  aspell0.60.6-3   GNU Aspell spell-checker
ii  ispell3.1.20.0-7 International Ispell (an interacti
pn  khelpcenter4  none (no description available)
ii  konsole   4:4.3.4-1  X terminal emulator for KDE 4

-- 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/20100218165627.9590.66681.report...@olivaw.celest.fr

Bug#516228: kmail: Empty trash only empty mail in selected groups

[Thomas Preud'homme]

Package: kmail
Version: 4:4.2.0-1
Severity: normal

Empty trash only delete mails from selected groups. All mail in
unselected groups (groups you can't see mails in) remains in trash. 
And after, even if I select remaining groups, I can't empty the trash
either (emptry trash is grayed) and I need to click on another folder
and then again on the trash to empty it, but after selecting groups
again.

-- System Information:
Debian Release: 5.0
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.28-1-amd64 (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 kmail depends on:
ii  kdebase-runtime   4:4.2.0-1  runtime components from the offici
ii  kdelibs5  4:4.2.0-3  core libraries for all KDE 4 appli
ii  kdepimlibs5   4:4.2.0-1  core libraries for KDE PIM 4 appli
ii  libc6 2.9-1  GNU C Library: Shared libraries
ii  libgcc1   1:4.3.3-4  GCC support library
ii  libkdepim44:4.2.0-1  KDE PIM library
ii  libkleo4  4:4.2.0-1  certificate based crypto library f
ii  libkontactinterfaces4 4:4.2.0-1  KDE Kontact interface library
ii  libkpgp4  4:4.2.0-1  gpg based crypto library for KDE
ii  libksieve44:4.2.0-1  KDE mail/news message filtering li
ii  libmimelib4   4:4.2.0-1  KDE mime library
ii  libphonon44:4.3.0-2  Phonon multimedia framework for Qt
ii  libqt4-dbus   4.4.3-2Qt 4 D-Bus module
ii  libqt4-network4.4.3-2Qt 4 network module
ii  libqt4-qt3support 4.4.3-2Qt 3 compatibility library for Qt 
ii  libqt4-xml4.4.3-2Qt 4 XML module
ii  libqtcore44.4.3-2Qt 4 core module
ii  libqtgui4 4.4.3-2Qt 4 GUI module
ii  libstdc++64.3.3-4The GNU Standard C++ Library v3
ii  perl  5.10.0-19  Larry Wall's Practical Extraction 
ii  phonon4:4.3.0-2  metapackage for Phonon multimedia 

Versions of packages kmail recommends:
ii  procmail  3.22-16Versatile e-mail processor

Versions of packages kmail suggests:
pn  clamav | f-prot-installer none (no description available)
ii  gnupg 1.4.9-4GNU privacy guard - a free PGP rep
ii  gnupg-agent   2.0.9-3.1  GNU privacy guard - password agent
ii  kaddressbook  4:4.2.0-1  KDE address book
ii  kleopatra 4:4.2.0-1  KDE Certificate Manager
ii  pinentry-gtk2 [pinentry-x11]  0.7.5-3GTK+-2-based PIN or pass-phrase en
ii  pinentry-qt [pinentry-x11]0.7.5-3Qt-based PIN or pass-phrase entry 
pn  spamassassin | bogofilter | a none (no description available)

-- 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

Bug#516229: kmail: Allow to choose which mails are counted in global new mails count

[Thomas Preud'homme]

Package: kmail
Version: 4:4.2.0-1
Severity: wishlist

Please provide a way to tell kmail which folder you want to count new
mail in global count. For example you want to know if there is new mails
in inbox but not in box you made for your mailing list.

-- System Information:
Debian Release: 5.0
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.28-1-amd64 (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 kmail depends on:
ii  kdebase-runtime   4:4.2.0-1  runtime components from the offici
ii  kdelibs5  4:4.2.0-3  core libraries for all KDE 4 appli
ii  kdepimlibs5   4:4.2.0-1  core libraries for KDE PIM 4 appli
ii  libc6 2.9-1  GNU C Library: Shared libraries
ii  libgcc1   1:4.3.3-4  GCC support library
ii  libkdepim44:4.2.0-1  KDE PIM library
ii  libkleo4  4:4.2.0-1  certificate based crypto library f
ii  libkontactinterfaces4 4:4.2.0-1  KDE Kontact interface library
ii  libkpgp4  4:4.2.0-1  gpg based crypto library for KDE
ii  libksieve44:4.2.0-1  KDE mail/news message filtering li
ii  libmimelib4   4:4.2.0-1  KDE mime library
ii  libphonon44:4.3.0-2  Phonon multimedia framework for Qt
ii  libqt4-dbus   4.4.3-2Qt 4 D-Bus module
ii  libqt4-network4.4.3-2Qt 4 network module
ii  libqt4-qt3support 4.4.3-2Qt 3 compatibility library for Qt 
ii  libqt4-xml4.4.3-2Qt 4 XML module
ii  libqtcore44.4.3-2Qt 4 core module
ii  libqtgui4 4.4.3-2Qt 4 GUI module
ii  libstdc++64.3.3-4The GNU Standard C++ Library v3
ii  perl  5.10.0-19  Larry Wall's Practical Extraction 
ii  phonon4:4.3.0-2  metapackage for Phonon multimedia 

Versions of packages kmail recommends:
ii  procmail  3.22-16Versatile e-mail processor

Versions of packages kmail suggests:
pn  clamav | f-prot-installer none (no description available)
ii  gnupg 1.4.9-4GNU privacy guard - a free PGP rep
ii  gnupg-agent   2.0.9-3.1  GNU privacy guard - password agent
ii  kaddressbook  4:4.2.0-1  KDE address book
ii  kleopatra 4:4.2.0-1  KDE Certificate Manager
ii  pinentry-gtk2 [pinentry-x11]  0.7.5-3GTK+-2-based PIN or pass-phrase en
ii  pinentry-qt [pinentry-x11]0.7.5-3Qt-based PIN or pass-phrase entry 
pn  spamassassin | bogofilter | a none (no description available)

-- 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