Re: Some comps cleanup

2015-12-07 Thread Kevin Fenzi
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

Re: Some comps cleanup

2015-12-07 Thread Vít Ondruch
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

Re: Some comps cleanup

2015-12-07 Thread Kalev Lember
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

Re: Some comps cleanup

2015-12-07 Thread Vít Ondruch
-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

Re: Some comps cleanup

2015-12-06 Thread Jerry James
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

Some comps cleanup

2015-12-06 Thread Kevin Fenzi
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

Re: Comps Cleanup

2013-08-28 Thread Kalev Lember
On 08/27/2013 07:52 PM, Bill Nottingham wrote: > Kalev Lember (kalevlem...@gmail.com) said: >> I'd like to be able to commit to master, check out the f20 branch, and >> 'git cherry-pick master'. > > Is that really that much difference than git diff | sed | patch? I believe it is, yes. Relying on

Re: Comps Cleanup

2013-08-28 Thread Mikolaj Izdebski
On 08/25/2013 01:17 AM, Till Maas wrote: > It seems that the following packages are stil mentioned in f20 or > f21 comps (I do not know which I checked) but are not in the i686 repo. > At least some of these packages are arch specific: > > ant-scripts ant-scripts fixed. Thanks, -- Mikolaj Izdeb

Re: Comps Cleanup

2013-08-27 Thread Bill Nottingham
Kalev Lember (kalevlem...@gmail.com) said: > I'd like to be able to commit to master, check out the f20 branch, and > 'git cherry-pick master'. Is that really that much difference than git diff | sed | patch? In any case, this would (as stated) require fixing the buildrawhide, buildbranced, and

Re: Comps Cleanup

2013-08-25 Thread drago01
On Sun, Aug 25, 2013 at 3:02 PM, Dennis Gilmore wrote: > Separate branches would break updates pushing. The tools can't be updated to use a different branch? Not sure which scripts / tools get used but that does not sound like an impossible thing. -- devel mailing list devel@lists.fedoraproject.

Re: Comps Cleanup

2013-08-25 Thread Dennis Gilmore
Separate branches would break updates pushing. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.-- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Comps Cleanup

2013-08-25 Thread Richard W.M. Jones
On Sun, Aug 25, 2013 at 11:10:17AM +0200, Kalev Lember wrote: > On 08/25/2013 01:17 AM, Till Maas wrote: > > the comps git repo currently contains comps files for EOL releases, > > which makes "grep" more cumbersome, because one needs to specify the > > current non-EOL releases to grep only in them

Re: Comps Cleanup

2013-08-25 Thread Richard W.M. Jones
On Sun, Aug 25, 2013 at 11:10:30AM +0200, Till Maas wrote: > On Sun, Aug 25, 2013 at 09:54:59AM +0100, Subhendu Ghosh wrote: > > On Aug 25, 2013 12:17 AM, "Till Maas" wrote: > > > > > > Hi, > > > > > > the comps git repo currently contains comps files for EOL releases, > > > which makes "grep" mor

Re: Comps Cleanup

2013-08-25 Thread Till Maas
On Sun, Aug 25, 2013 at 09:54:59AM +0100, Subhendu Ghosh wrote: > On Aug 25, 2013 12:17 AM, "Till Maas" wrote: > > > > Hi, > > > > the comps git repo currently contains comps files for EOL releases, > > which makes "grep" more cumbersome, because one needs to specify the > > current non-EOL releas

Re: Comps Cleanup

2013-08-25 Thread Kalev Lember
On 08/25/2013 01:17 AM, Till Maas wrote: > the comps git repo currently contains comps files for EOL releases, > which makes "grep" more cumbersome, because one needs to specify the > current non-EOL releases to grep only in them. Also it makes the default > make target take unecessarily long, beca

Re: Comps Cleanup

2013-08-25 Thread Subhendu Ghosh
On Aug 25, 2013 12:17 AM, "Till Maas" wrote: > > Hi, > > the comps git repo currently contains comps files for EOL releases, > which makes "grep" more cumbersome, because one needs to specify the > current non-EOL releases to grep only in them. Also it makes the default > make target take unecessa

Comps Cleanup

2013-08-24 Thread Till Maas
Hi, the comps git repo currently contains comps files for EOL releases, which makes "grep" more cumbersome, because one needs to specify the current non-EOL releases to grep only in them. Also it makes the default make target take unecessarily long, because it build all comps including the EOL one