Your message dated Sat, 09 Nov 2013 15:02:38 +1100 with message-id <2667267.MOI9vr7skI@acer> and subject line Fwd: K3b 2.0.0-1 uploaded to unstable - bug pong - closing has caused the Debian Bug report #399139, regarding Cdrskin as default 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.) -- 399139: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=399139 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: k3b Severity: wishlist It would be great if we could enable cdrskin instead of wodim by default so we would get a lot of testing. It is understandable that this would 'cause a lot of problems, and bugs, but we have to go through that if we want to have a happy burning future under linux, since cdrskin is based on libburn. http://libburn.pykix.org Kind regards
--- End Message ---
--- Begin Message ---Nothing further. Closing ---------- Forwarded Message ---------- Subject: Bug#491704: K3b 2.0.0-1 uploaded to unstable - bug ping Date: Sun, 4 Jul 2010, 14:29:07 From: Mark Purcell <m...@debian.org> CC: k...@packages.debian.org 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. 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 is still valid with version 2.0. If your bug has been resolved then please send an email to xxxx- d...@bugs.debian.org, where xxxx is your Debian bug report number, giving your description of how the bug is working. If your bug has not been resolved, then please first check upstream reports for a duplicate, and then send an update email to x...@bugs.debian.org, stating that the bug is still valid. https://bugs.kde.org/buglist.cgi?quicksearch=k3b If we don't hear from you in the near term, then we may have to close your report as without moreinfo most reports are difficult to reproduce. 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. -----------------------------------------
Description: This is a digitally signed message part.
--- End Message ---
_______________________________________________ pkg-kde-extras mailing list email@example.com http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras