Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

libmodplug ghost distro mapping #98

Closed
scop opened this issue Feb 24, 2015 · 2 comments
Closed

libmodplug ghost distro mapping #98

scop opened this issue Feb 24, 2015 · 2 comments
Assignees
@pypingou

Comments

@scop
Copy link

scop commented Feb 24, 2015

I tried to add the libmodplug project, got an internal server error while adding it, and now I cannot add a distro mapping (Fedora, libmodplug) for it, the service tells me "Could not edit the mapping of libmodplug on Fedora, there is already a package libmodplug on Fedora" but the mapping is not actually shown in the project mappings view.

https://release-monitoring.org/project/5669/
@scop
Copy link
Author

scop commented Feb 24, 2015

Oh, the reason seems to be that the mapping actually does exist, but it's in the modplug-xmms project which is wrong. So there are actually two bugs to fix here:

  1. The service should say where an existing mapping exists. In this case it should have mentioned that the mapping is in the modplug-xmms project.
  2. There doesn't seem to be any way to delete a mapping so I cannot fix the situation. The modplug-xmms project also contains a mapping for modplugtools which is equally wrong.

@pypingou pypingou self-assigned this Feb 25, 2015
pypingou added a commit that referenced this issue Feb 25, 2015
@pypingou
More user information when mapping a project fails
3f66da0 
If a mapping fails because there is already a package with this name on
that distribution, until now we only mentioned this to the user, now we
are also saying as part of which project this package can be found.

Fixes #98
@pypingou
Copy link
Member

The first point is fixed in the commit above, the second one is present but apparently only accessible to admins.

Question becomes: do we want to make this more open?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pypingou pypingou

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@scop @pypingou