On 05/21/2016 12:28 AM, Kevin Fenzi wrote:
> On Fri, 20 May 2016 09:10:58 -0600
> Orion Poplawski wrote:
>> In some sense I think it's more important to be run for branched.
>> Are the branched builds run against updates-testing? or only updates
>> + overrides? I'm thinking
On Fri, 20 May 2016 09:10:58 -0600
Orion Poplawski wrote:
> I will just note that there definitely is a reasonable amount of
> churn in Rawhide that does tend to trigger notices of temporary build
> failures when say a soname was updated and dependent packages not yet
>
On 05/19/2016 10:52 AM, Kevin Fenzi wrote:
> On Thu, 19 May 2016 11:15:02 +0200
> Mikolaj Izdebski wrote:
>
>>> Perhaps we could look into just mass enabling it for all packages
>>> now?
>>
>> Perhaps yes, but...
>>
>> Some people are not interested in Koschei at all. It
On Thu, 19 May 2016 11:15:02 +0200
Mikolaj Izdebski wrote:
> Since I heard several requests about that, I will try to enable EPEL 7
> (in staging for now). If it goes well then we can think about
> enabling EPEL 6 or Fedora branches too.
ok. Thanks. There are many fewer
On 05/19/2016 12:40 AM, Kevin Fenzi wrote:
> On Wed, 18 May 2016 05:03:51 +0200
> Mikolaj Izdebski wrote:
>> Last week Koschei [1] was updated to latest upstream release (1.6.1).
>> The new version comes with one particularly interesting feature -
>> Koschei is now able to
Dne 19.5.2016 v 10:47 Mikolaj Izdebski napsal(a):
> On 05/18/2016 10:40 AM, Vít Ondruch wrote:
>> Could you please enable CI for ruby? Or actually the ruby-rails group
>> for every Fedora branch?
> It doesn't work this way. Once new targets are added to Koschei, all
> packages will be monitored
On 05/18/2016 08:37 PM, Raphael Groner wrote:
> +1 branched/alpha (could help with upcoming mass rebuild issues)
Mass rebuilds are done in rawhide, before branching.
--
Mikolaj Izdebski
Software Engineer, Red Hat
IRC: mizdebsk
--
devel mailing list
devel@lists.fedoraproject.org
On 05/18/2016 10:40 AM, Vít Ondruch wrote:
> Could you please enable CI for ruby? Or actually the ruby-rails group
> for every Fedora branch?
It doesn't work this way. Once new targets are added to Koschei, all
packages will be monitored there. It's all or nothing.
--
Mikolaj Izdebski
Software
On Wed, 18 May 2016 05:03:51 +0200
Mikolaj Izdebski wrote:
> TL;DR Koschei now supports targets other than rawhide (not enabled
> yet) and should correctly handle weak and rich deps.
>
> Full version:
>
> Last week Koschei [1] was updated to latest upstream release
> Koschei is now able to track more than one package collection at time,
> which means that it could be possible to use it for Fedora branches
> other than just rawhide, for EPEL, or even for side tags in Koji.
> Currently only rawhide is enabled, but if there's enough interest then
> it should be
Hi Mikolaj,
This is sweet! Thx.
Could you please enable CI for ruby? Or actually the ruby-rails group
for every Fedora branch?
Best,
Vít
Dne 18.5.2016 v 05:03 Mikolaj Izdebski napsal(a):
> TL;DR Koschei now supports targets other than rawhide (not enabled
> yet) and should correctly
11 matches
Mail list logo