Re: COPR and new chroot naming

2017-02-22 Thread Kevin Kofler
Kevin Fenzi wrote: > If we move back to having a rawhide/devel/master repo the problem > becomes "which rawhide" ? if you build something in that branch a year > ago, what are the chances it will still work? I have packages built in 2007 that still work (in the CalcForge repository).

Re: COPR and new chroot naming

2017-02-21 Thread Michal Novotny
On Tue, Feb 21, 2017 at 5:15 PM, Kevin Fenzi wrote: > On Tue, 21 Feb 2017 11:00:15 +0100 > Michal Novotny wrote: > > > On Tue, Feb 21, 2017 at 10:28 AM, Vít Ondruch > > wrote: > > > > > I honestly don't understand what is purpose of the

Re: COPR and new chroot naming

2017-02-21 Thread Catalin
Many changes into Fedora area is instability with development and for attracting new developers. I advocate the development of overlapping time periods only reason : the developers implement the software into many distributions. That allow to make changes in time. ... a real problem is spam and

Re: COPR and new chroot naming

2017-02-21 Thread Kevin Fenzi
On Tue, 21 Feb 2017 11:00:15 +0100 Michal Novotny wrote: > On Tue, Feb 21, 2017 at 10:28 AM, Vít Ondruch > wrote: > > > I honestly don't understand what is purpose of the f26 vs master. > > Why we have empty master currently (speaking of dist-git)? master

Re: COPR and new chroot naming

2017-02-21 Thread Pavel Raiskup
On Tuesday, February 21, 2017 11:00:15 AM CET Michal Novotny wrote: > On Tue, Feb 21, 2017 at 10:28 AM, Vít Ondruch wrote: > > > I honestly don't understand what is purpose of the f26 vs master. Why we > > have empty master currently (speaking of dist-git)? master should be

Re: COPR and new chroot naming

2017-02-21 Thread Michal Novotny
On Tue, Feb 21, 2017 at 10:28 AM, Vít Ondruch wrote: > I honestly don't understand what is purpose of the f26 vs master. Why we > have empty master currently (speaking of dist-git)? master should be the > same as rawhide, as it is in Fedora. > Yes, I think that makes more