Re: https://bugzilla.redhat.com/show_bug.cgi?id=1284183
I have removed a bunch of packages that have been orphaned/retired from comps, but there's still more to be done there.
There's also a number of packages that have changed name that should get updated.
Perhaps someone would care to write a checker script here?
Check each package in comps, make sure it is no retired/orphaned/missing and of those look for packages that now provide that name?
kevin
On Sun, Dec 6, 2015 at 12:59 PM, Kevin Fenzi kevin@scrye.com wrote:
Perhaps someone would care to write a checker script here?
Check each package in comps, make sure it is no retired/orphaned/missing and of those look for packages that now provide that name?
It would be good to also check for dangling references inside comps. For example, in the servers category, the grouplist includes <groupid>clustering</groupid>, but there is no clustering group definition to be found.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Can somebody explain me why Rawhide comps are called F24? Trying to use "git blame" and surprisingly (or not that much), almost every line was created by Kevin Fenzi. Why we are using git if we break the history this way? How can I find what was reason to add something, unless I really want to dig through history of every comps file.
A would appreciate if the comps-f24.xml.in could be renamed to comps-rawhide.xml.in to keep the history.
Vít
Dne 6.12.2015 v 20:59 Kevin Fenzi napsal(a):
Re: https://bugzilla.redhat.com/show_bug.cgi?id=1284183
I have removed a bunch of packages that have been orphaned/retired from comps, but there's still more to be done there.
There's also a number of packages that have changed name that should get updated.
Perhaps someone would care to write a checker script here?
Check each package in comps, make sure it is no retired/orphaned/missing and of those look for packages that now provide that name?
kevin
-- devel mailing list devel@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
On 12/07/2015 11:42 AM, Vít Ondruch wrote:
Can somebody explain me why Rawhide comps are called F24? Trying to use "git blame" and surprisingly (or not that much), almost every line was created by Kevin Fenzi. Why we are using git if we break the history this way? How can I find what was reason to add something, unless I really want to dig through history of every comps file.
A would appreciate if the comps-f24.xml.in could be renamed to comps-rawhide.xml.in to keep the history.
Another way might be to use git branches instead of separate files: have 'master' branch for rawhide, 'f23' for Fedora 23 etc and use the same file name (comps.xml.in) in all the branches. That would be analogous to the way the packages git is set up.
This would make it much easier to put the same change to different branches (just use 'git cherry-pick', instead of having to do the same change several times in different files as is now) and would make it easier to use 'git blame' for the history.
Dne 7.12.2015 v 11:56 Kalev Lember napsal(a):
On 12/07/2015 11:42 AM, Vít Ondruch wrote:
Can somebody explain me why Rawhide comps are called F24? Trying to use "git blame" and surprisingly (or not that much), almost every line was created by Kevin Fenzi. Why we are using git if we break the history this way? How can I find what was reason to add something, unless I really want to dig through history of every comps file.
A would appreciate if the comps-f24.xml.in could be renamed to comps-rawhide.xml.in to keep the history.
Another way might be to use git branches instead of separate files: have 'master' branch for rawhide, 'f23' for Fedora 23 etc and use the same file name (comps.xml.in) in all the branches. That would be analogous to the way the packages git is set up.
This would make it much easier to put the same change to different branches (just use 'git cherry-pick', instead of having to do the same change several times in different files as is now) and would make it easier to use 'git blame' for the history.
Even better. I just mildly remember this was already proposed and rejected, can't find where and why :/
Vít
On Mon, 7 Dec 2015 12:20:27 +0100 Vít Ondruch vondruch@redhat.com wrote:
Dne 7.12.2015 v 11:56 Kalev Lember napsal(a):
On 12/07/2015 11:42 AM, Vít Ondruch wrote:
Can somebody explain me why Rawhide comps are called F24? Trying to use "git blame" and surprisingly (or not that much), almost every line was created by Kevin Fenzi. Why we are using git if we break the history this way? How can I find what was reason to add something, unless I really want to dig through history of every comps file.
A would appreciate if the comps-f24.xml.in could be renamed to comps-rawhide.xml.in to keep the history.
Another way might be to use git branches instead of separate files: have 'master' branch for rawhide, 'f23' for Fedora 23 etc and use the same file name (comps.xml.in) in all the branches. That would be analogous to the way the packages git is set up.
This would make it much easier to put the same change to different branches (just use 'git cherry-pick', instead of having to do the same change several times in different files as is now) and would make it easier to use 'git blame' for the history.
Even better. I just mildly remember this was already proposed and rejected, can't find where and why :/
I think it was just setup this way long ago and it's effort to change it.
If there's people willing to do the work, I personally have no objection. Might be good to run past the releng list and fesco tho.
kevin