Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#52979 - [rust] package name and group name are the same
Attached to Project:
Community Packages
Opened by Jonathan Kotta (jpkotta) - Wednesday, 15 February 2017, 18:52 GMT
Last edited by Johannes Löthberg (demize) - Thursday, 27 April 2017, 19:51 GMT
Opened by Jonathan Kotta (jpkotta) - Wednesday, 15 February 2017, 18:52 GMT
Last edited by Johannes Löthberg (demize) - Thursday, 27 April 2017, 19:51 GMT
|
DetailsDescription:
The rust package name collides with the group name. They should be different, because pacman prioritizes packages over groups, meaning you can't install by group if the package name is the same (https://bugs.archlinux.org/task/27660). AFAIK, this is the only such group/package name conflict in Arch at this time (`for i in $(pacman -Sg) ; do pacman -Sg $i | grep -E "^(\w+) \1$" ; done`). |
This task depends upon
I think it is problem with pacman that package names and group names can collide.
If someone should ever name a package "base" or "base-devel", it would result in huge problems.
If pacman had a flag for specifying if a given string is the name of a package or a group, this should not be an issue.
Will consider making the requested changes for the rust package, for now, though.
bug 27660, it sounds like the pacman maintainers aren't going to change it.