Description of problem: Please add more properties available from primary.xml: <rpm:license>LGPLv2+</rpm:license> <rpm:vendor>Fedora Project</rpm:vendor> <rpm:group>System Environment/Libraries</rpm:group> <rpm:buildhost>buildhw-09.phx2.fedoraproject.org</rpm:buildhost> <rpm:sourcerpm>hawkey-0.5.1-1.fc21.src.rpm</rpm:sourcerpm> group property is most wanted for me, but vendor and buildhost should be useful too. license and sourcerpm are currently available. Version-Release number of selected component (if applicable): hawkey-0.5.7-1.fc22.x86_64
If you mean package group defined in spec file then it's AFAIK its usage is deprecated according to Fedora guidelines.
But there is nothing what can replace them. Is it possible to add this feature at least until there will be a functional replacement? Groups from repository are filled only for some packages. I use group for my package list at: http://www.salstar.sk/rpmbrowse/ Try to look at group stats: http://www.salstar.sk/rpmbrowse/stats (scroll down to group stats) 238253 has no group set. Aprox. 5000 packages has it.
Ok, tell us your use case so we can find you alternative way to get it.
As I wrote, my http://www.salstar.sk/rpmbrowse/ uses group attribute to list packages for an group. Useful if user searches for similar packages, knowing it's group. My rpmbrowse runs on Fedora, but can collect rpm information from other distributions too, for example from CentOS5 and CentOS6, but from other also from other repositories (rpmfusion, ...), which don't use other methods to group packages. I think it's also not planned to use for CentOS<=6, so there is no other way, how to use grouping feature. Other mentioned tags are also useful for creating rpm databases. I think other rpm databases should use these informations too. I don't know if there are others, but if they will be developed, I think access to more information should be useful. For yum this worked well, so this looks like an regression on yum to dnf update. Even if group attribute is required for listing packages in groups, other attributes (sourcerpm, license, buildhost, vendor) are useful when listing information about an package. Please add them too if possible. Thank you.
Your project is a useful tool but using the group tag is not aligned with Fedora goals [1]. For listing packages in Categories is being created Fedora Developer Portal (~web version of Gnome Software). If anyone wants this feature then post a comment to raise it's priority. [1] https://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/Packagers_Guide/chap-Packagers_Guide-Spec_File_Reference-Preamble.html
*** Bug 1270402 has been marked as a duplicate of this bug. ***
I would appreciate this feature because Mageia heavily depends on this property for organization of its packages.
I've added the necessary hooks in the Hawkey API in the mega-merge libhif branch to retrieve the Group tag, and it was merged in earlier today[1]. At this point, DNF needs to expose that information through its API and CLI. [1]: https://github.com/rpm-software-management/libhif/pull/65
This is now present in the master branch of libhif, and the property will be available in the next release.
This is also now implemented in hawkey-0.6.3, released earlier today. I do not know if Fedora will get it, though.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Just for information, hawkey-0.6.3 is a part of Fedora 24 and group property works well. Thanks you.