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 541334 - compilation albums are separated
compilation albums are separated
Status: RESOLVED DUPLICATE of bug 517671
Product: banshee
Classification: Other
Component: Importing
1.0.0
Other All
: Normal minor
: 1.x
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-07-03 01:07 UTC by Jacob Peddicord
Modified: 2008-07-03 02:10 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jacob Peddicord 2008-07-03 01:07:56 UTC
Please describe the problem:
When importing a collection of songs, Banshee seems to have a one-to-many relationship with artists and albums: an artist can have many albums, but an album can only be assigned to one artist. This means that when a compilation album is imported (different artist for each song) it creates a new album entry for each different artist. This should be a many-to-many relationship in that an album can have more than one artist and not split itself up. (See Rhythmbox [heh] for an example.)

Steps to reproduce:
1. Import a set of songs from the same album but with different artists
2. Notice how the Albums pane has more than one album entry for the same album, but with a different artist

Actual results:
The Albums pane has more than one album entry for the same album, but with a different artist

Expected results:
There should only be one entry per album, even if it means more than one artist is displayed

Does this happen every time?
Yes

Other information:
If not default, at least make it an option in case there are some who think it should sort albums as it does now
Comment 1 Andrew Conkling 2008-07-03 02:10:40 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 517671 ***