Your message dated Sun, 11 Mar 2007 18:23:26 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#394997: closed by "Olivier Vitrat" <[EMAIL PROTECTED]>
(#394997: Can't reproduce this bug)
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: korganizer
Version: 4:3.5.5-1
Severity: minor
When I start korganizer from the command line I see in the terminal:
ConditionalOffset: 1.0.107, condition=0
Date is a 1
ConditionalOffset: 25.11.107, condition=0
Date is a 2
ConditionalOffset: 1.7.107, condition=0
Date is a 3
[...]
This goes on an on, while I navigate around in korganizer...
*t
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing'), (50, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages korganizer depends on:
ii kdelibs4c2a 4:3.5.5a.dfsg.1-1 core libraries and binaries for al
ii libart-2.0-2 2.3.17-1 Library of functions for 2D graphi
hi libaudio2 1.8-2 The Network Audio System (NAS). (s
ii libc6 2.3.6.ds1-4 GNU C Library: Shared libraries
hi libfontconfig1 2.4.1-2 generic font configuration library
hi libfreetype6 2.2.1-5 FreeType 2 font engine, shared lib
hi libgcc1 1:4.1.1-16 GCC support library
ii libice6 1:1.0.1-2 X11 Inter-Client Exchange library
ii libidn11 0.6.5-1 GNU libidn library, implementation
hi libjpeg62 6b-13 The Independent JPEG Group's JPEG
ii libkcal2b 4:3.5.5-1 KDE calendaring library
ii libkdepim1a 4:3.5.5-1 KDE PIM library
ii libkpimexchange1 4:3.5.5-1 KDE PIM Exchange library
ii libkpimidentities1 4:3.5.5-1 KDE PIM user identity information
ii libpng12-0 1.2.8rel-5.2 PNG library - runtime
ii libqt3-mt 3:3.3.6-4 Qt GUI Library (Threaded runtime v
ii libsm6 1:1.0.1-3 X11 Session Management library
ii libstdc++6 4.1.1-16 The GNU Standard C++ Library v3
ii libx11-6 2:1.0.0-9 X11 client-side library
hi libxcursor1 1.1.7-4 X cursor management library
ii libxext6 1:1.0.1-2 X11 miscellaneous extension librar
hi libxft2 2.1.8.2-8 FreeType-based font drawing librar
ii libxi6 1:1.0.1-3 X11 Input extension library
ii libxinerama1 1:1.0.1-4.1 X11 Xinerama extension library
ii libxrandr2 2:1.1.0.2-4 X11 RandR extension library
ii libxrender1 1:0.9.1-3 X Rendering Extension client libra
ii libxt6 1:1.0.2-2 X11 toolkit intrinsics library
ii perl 5.8.8-6.1 Larry Wall's Practical Extraction
ii zlib1g 1:1.2.3-13 compression library - runtime
Versions of packages korganizer recommends:
ii kghostview 4:3.5.5-1 PostScript viewer for KDE
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 4:3.5.6-dfsg.1-1
On Sunday 11 March 2007, Tomas Pospisek wrote:
> On Sat, 10 Mar 2007, Olivier Vitrat wrote:
> > Hi, I can't reproduce this with Korganizer version 3.5.6-dfsg.1-1
> > Closing this bug.
>
> Ummm Olivier, 3.5.6-dfsg.1-1 is only in experimental - is it correct
> procedure to close bugs fixed by experimental deb packages only (as in
> this case?). (I'd be extra careful... there's no guarantee that
> experimental will propagate to unstable->testing as far as I understand
> it).
Hi people!
Version tracking is a quite new feature which still confuses many people, but
the official answer should be, as far as I have been told until now, is that
closing with a version is the correct thing to do. The fixed-in-experimental
tag is not being used much any more, now that the bug tracking system has
nice version tracking.
If you look at the bug page
http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=korganizer;dist=unstable
(notice the ;dist=unstable), this bug will show up as being open for unstable,
but also marked as done in <some-later-version>
If we (the maintainers) somehow does not make sure that the bug is marked as
fixed in whatever version later uploaded to unstable, this bug will still be
shown on the ;dist=unstabel page until it is marked as closed in a changelog
in unstable.
Thank you for your questions. The quick answer is that Olivier is doing the
right thing. I am marking this bug as closed in the version in experimental
If you look at this page in the next days:
http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=kde-style-serenity;dist=unstable
you will see one open bug, where the text in the closer description actually
says Done: <me> and fixed in the version currently in experimental. But it
still shows up in the "Outstanding bugs " section.
Thank you for your time and both of your efforts to try to make the debian
bugtracking system as accurate as possible.
/Sune
--
How may I do for receiving from a forward?
You should reset a SIMM for forwarding from the desktop.
pgpfgkPvixT3r.pgp
Description: PGP signature
--- End Message ---
