Bug#682077: marked as done (braindump: No way to save, print, export?)
Your message dated Thu, 19 Jul 2012 20:12:59 +0200
with message-id <201207192013.00712.sune@debian.org>
and subject line Re: Bug#682077: braindump: No way to save, print, export?
has caused the Debian Bug report #682077,
regarding braindump: No way to save, print, export?
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
682077: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682077
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: braindump
Version: 1:2.4.3-1
Severity: grave
Justification: renders package unusable
The File menu has only one entry ("Quit") and I find no way to save,
export or print... (may I have failed to notice some interface detail?)
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores)
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 braindump depends on:
ii calligra-libs 1:2.4.3-1
ii kde-runtime 4:4.8.4-1
ii libc6 2.13-33
ii libkdecore5 4:4.8.4-3
ii libkdeui5 4:4.8.4-3
ii libkio5 4:4.8.4-3
ii libkparts4 4:4.8.4-3
ii libqt4-svg 4:4.8.2-1
ii libqt4-xml 4:4.8.2-1
ii libqtcore4 4:4.8.2-1
ii libqtgui4 4:4.8.2-1
ii libqtwebkit4 2.2.1-4+b1
ii libstdc++6 4.7.1-2
braindump recommends no packages.
braindump suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Thursday 19 July 2012 19:40:53 AN support wrote:
> -- that, in spite of it, explicitly being able to control where to save
> would be convenient;
> -- and that, because other capabilities (exporting, printing) seem also
> to be anomalously missing, it all seemed to be the result of some bug,
> anyway...
Then the bug is entirely different than what you first described. What you
described was a dataloss bug (you can create data and then it disappears) at a
severity that basically says "this should be the most important thing on the
maintainers plate", while in reality it is actually just because you disagree
with where upstream so far has put their priorities.
So, please take it up with upstream wether or not they think your requests
makes sense. I'm closing this bug as there is nothing there can be done about
it from the debian side, except choosing wether or not to remove the actual
application based on this bug report, which I really think there isn't.
You can reach upstream on forum.kde.org or on kde's calligra emaillists.
/Sune
--- End Message ---
Reply to: