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 #421865, regarding Regression: Won't rip then burn from audio CD in one step 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.) -- 421865: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=421865 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: k3b Version: 1.0.1-1 Severity: normal In k3b 0.12, you could put an audio CD in your CD-RW drive, make a new audio CD project in k3b, drag the tracks from the top pane (representing the inserted audio CD) to the bottom pane, click Burn, and k3b would rip the tracks, eject the audio CD, take a blank CD, and burn the tracks to the blank CD. This is very handy for copying an audio CD that does not have CD Text, since you can add it yourself. But in k3b 1.0.1, when you follow those steps and then click Burn, the burn dialog says "Please insert an empty CD-R(W) medium..." in the "Burn medium" area. The only way it will proceed is if you choose "Only create image", but that would mean that you'd have to then take the image that was created and burn it in a separate step. --- System information. --- Architecture: i386 Kernel: Linux 2.6.18-4-k7 Debian Release: testing/unstable 900 testing ftp.us.debian.org 900 testing ftp.sunet.se 800 unstable ftp.us.debian.org 800 unstable ftp.sunet.se 500 stable security.debian.org 500 edgy-cafuego ubuntu.cafuego.net 500 edgy wine.budgetdedicated.com 1 experimental ftp.us.debian.org --- Package information. --- Depends (Version) | Installed =============================================-+-======================= kdelibs4c2a (>= 4:3.5.5-1) | 4:3.5.5a.dfsg.1-8 libacl1 (>= 2.2.11-1) | 2.2.42-1 libart-2.0-2 (>= 2.3.16) | 2.3.17-1 libattr1 (>= 2.4.4-1) | 1:2.4.32-1.1 libaudio2 | 1.8-4 libc6 (>= 2.3.6-6) | 2.3.6.ds1-13 libdbus-1-3 (>= 0.94) | 1.0.2-1 libdbus-qt-1-1c2 (>= 0.62.git.20060814) | 0.62.git.20060814-2 libdvdread3 (>= 0.9.6) | 0.9.7-3 libexpat1 (>= 1.95.8) | 1.95.8-3.4 libfam0 | 2.7.0-12 libfontconfig1 (>= 2.4.0) | 2.4.2-1.2 libfreetype6 (>= 2.2) | 2.2.1-5 libgcc1 (>= 1:4.1.1-12) | 1:4.1.1-21 libhal1 (>= 0.5) | 0.5.8.1-9 libice6 (>= 1:1.0.0) | 1:1.0.3-2 libidn11 (>= 0.5.18) | 0.6.5-1 libjpeg62 | 6b-13 libk3b3 (>= 1.0.1) | 1.0.1-1 libmusicbrainz4c2a (>= 2.1.4) | 2.1.4-1 libpng12-0 (>= 1.2.13-4) | 1.2.15~beta5-1 libqt3-mt (>= 3:3.3.7) | 3:3.3.7-4 libsm6 | 1:1.0.2-2 libstdc++6 (>= 4.1.1-12) | 4.1.1-21 libx11-6 | 2:1.0.3-7 libxcursor1 (>> 1.1.2) | 1.1.7-4 libxext6 | 1:1.0.1-2 libxft2 (>> 2.1.1) | 2.1.12-2 libxi6 | 1:1.0.1-4 libxinerama1 | 1:1.0.1-4.1 libxrandr2 | 2:184.108.40.206-5 libxrender1 | 1:0.9.1-3 libxt6 | 1:1.0.5-2 zlib1g (>= 1:1.2.1) | 1:1.2.3-13 wodim | 9:1.1.4-1 OR cdrskin | cdparanoia (>= 3a9.8) | 3.10+debian~pre0-4 genisoimage | 9:1.1.4-1 kdelibs-data (>= 4:3.1.4-2) | 4:3.5.5a.dfsg.1-8 kdebase-bin | 4:3.5.5a.dfsg.1-6 cdrdao (>= 1.1.7-5) | 1:1.2.2-6
Description: PGP signature
--- 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. -----------------------------------------
Description: This is a digitally signed message part.
--- End Message ---
_______________________________________________ pkg-kde-extras mailing list email@example.com http://lists.alioth.debian.org/mailman/listinfo/pkg-kde-extras