Your message dated Sun, 4 Jul 2010 14:46:22 +1000
with message-id <201007041446.24245....@debian.org>
and subject line K3b 2.0.0-1 uploaded to unstable - bug ping
has caused the Debian Bug report #463877,
regarding Verification fails despite md5sums being the same
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 ow...@bugs.debian.org
immediately.)
--
463877: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=463877
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: K3b
Version: 1.0.4-3
I installed K3b on Lenny from official packages.
After burning an ISO of data CD or DVD
with option "VerifY written data", at the end
of this operation I receive the message:
"Data written on track 1 differ from original".
However, the md5sum of ISO is the same
ot that of the new CD. In effect, burning
is correct, only the verification fails.
I'm not able to determine if it's a bug
of K3b or of its Debian version.
I'm using Debian Lenny with kernel 2.6.24
compiled by myself.
Thanx
MS
--
linux user no.: 353546
public key at http://keyserver.linux.it
--- End Message ---
--- Begin Message ---
Dear submitter,
Some time ago you filed a report in the Debian bug tracking system against the
k3b package, http://bugs.debian.org/k3b
Upstream have now declared a major milestone and released K3b version 2.0,
which has now been uploaded to Debian unstable. Upstream have claimed that your
bug has been fixed-upstream via the forwarded link from to the upstream KDE
Bugzilla, thus we are now closing your Debian report.
We have a fairly large backlog on bugs reported against K3b and require your
assistance.
Could I ask you to install the K3b package from unstable and verify that your
report has been resolved with version 2.0.
If your bug has been resolved then there is no need for any further action you
your part.
If your bug has not been resolved, then please first check upstream reports for
the reason upstream have closed their report. Then please add further comments
against the upstream report and if necessary reopen both the upstream and
Debian bug reports.
https://bugs.kde.org/buglist.cgi?quicksearch=k3b
Thanks for your assistance in working with Debian K3b.
Mark
====================================================================================
The Debian team values users reports, but we are busy, and so we
kindly ask you to access the upstream support facilities:
There is a user mailing list which maybe used to get support:
http://lists.sourceforge.net/lists/listinfo/k3b-user
To post a message to all the list members, send email to
k3b-u...@lists.sourceforge.net.
If you know that the bug you want to report is in the "upstream"
code then please check/ file against the KDE Bug tracking system:
https://bugs.kde.org/buglist.cgi?quicksearch=k3b
You can also report bugs directly upstream using the K3b Help:Report Bug
menu entry.
If you feel that the bug is one that other Debian users should
know about then you are welcome to file a report in the Debian BTS
as well. Please keep in mind, however, that managing bug reports
is part of the maintainers' workload.
As a minimum we ask that you Cc: k3b-u...@lists.sourceforge.net any
reports you file in the Debian Bug Tracking system so that upstream
are aware of the issue you are reporting.
-----------------------------------------
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
_______________________________________________
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-kde-extras
