On Mon, 7 Dec 2015 12:20:27 +0100
Vít Ondruch 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
> >> ever
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
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 re
-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 rea
On Sun, Dec 6, 2015 at 12:59 PM, Kevin Fenzi 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
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
