After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 552976 - "Rescan music library" adds podcasts to the music library
"Rescan music library" adds podcasts to the music library
Status: RESOLVED FIXED
Product: banshee
Classification: Other
Component: Importing
1.3.0
Other Linux
: Normal minor
: 1.4.2
Assigned To: Banshee Maintainers
Banshee Maintainers
: 557039 561912 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-09-20 05:43 UTC by Michael Martin-Smucker
Modified: 2009-01-08 15:54 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Michael Martin-Smucker 2008-09-20 05:43:12 UTC
By default (and as far as I can tell this isn't changeable) podcasts are downloaded to a Podcasts folder inside the music library folder.  This means that when the music library folder is rescanned for new music, all of the podcasts are found and imported into the regular music library.  It would be nice if the podcast folder would be ignored on a rescan, or if Podcasts could be downloaded to a location outside of the normal music folder.
Comment 1 Bertrand Lorentz 2008-09-20 09:12:00 UTC
This is somewhat related to bug #535025.
Comment 2 Bertrand Lorentz 2008-10-20 16:58:00 UTC
*** Bug 557039 has been marked as a duplicate of this bug. ***
Comment 3 Bertrand Lorentz 2008-11-22 13:43:27 UTC
*** Bug 561912 has been marked as a duplicate of this bug. ***
Comment 4 Gabriel Burt 2009-01-07 20:53:43 UTC
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.
Comment 5 Michael Martin-Smucker 2009-01-08 06:17:38 UTC
Just out of curiosity, how was this bug fixed?  Can the user specify a specific folder for podcasts, or is the directory ~/Music/Podcasts just blacklisted?  Or I could just wait for 1.4.2 and find out for myself.
Comment 6 Gabriel Burt 2009-01-08 15:54:35 UTC
It's a hacky blacklist, for now.