Dne 24.8.2017 v 13:58 Cheng Ye napsal(a):
Hi,
Making the builddir accessible for failed build would be helpful. Some test
suits will store log in a file in buildir without echoing anything else
helpful. Without access to builddir, it could be difficult to debug. However,
copying the builddi
Hi,
Making the builddir accessible for failed build would be helpful. Some test
suits will store log in a file in buildir without echoing anything else
helpful. Without access to builddir, it could be difficult to debug. However,
copying the builddir from mock directory to somewhere accessibl
Dne 24.8.2017 v 04:10 Rudolf Kastl napsal(a):
Hey,
I am currently maintaining llvm trunk and mesa git snapshot repos for f25 and f26 at:
https://copr.fedorainfracloud.org/coprs/che.
One thing i would love to see is the ability to have a buildrepo and a release repo and beeing able to sync fro
2017-08-22 5:17 GMT+02:00 Michal Novotny :
> Hello,
>
> we will have soon a planning meeting that should determine a more long-term
> strategy and bring us to a team agreement on what COPR currently is and what
> it should be in half a year or so.
>
> I would like to kindly ask for some input here
Hello Rudolf,
On Thu, Aug 24, 2017 at 4:10 AM, Rudolf Kastl wrote:
> Hey,
>
> I am currently maintaining llvm trunk and mesa git snapshot repos for f25
> and f26 at: https://copr.fedorainfracloud.org/coprs/che.
>
> One thing i would love to see is the ability to have a buildrepo and a
> release
Hey,
I am currently maintaining llvm trunk and mesa git snapshot repos for f25
and f26 at: https://copr.fedorainfracloud.org/coprs/che.
One thing i would love to see is the ability to have a buildrepo and a
release repo and beeing able to sync from build to release once a complete
buildchain succ
On Tuesday, August 22, 2017 5:03:06 PM CEST Michal Novotny wrote:
> On Tue, Aug 22, 2017 at 4:40 PM, Kamil Dudka wrote:
> > On Tuesday, August 22, 2017 1:51:44 PM CEST Michal Novotny wrote:
> > > Hey Kamil,
> > >
> > > On Tue, Aug 22, 2017 at 12:07 PM, Kamil Dudka wrote:
> > > > On Tuesday, Augu
On Tue, Aug 22, 2017 at 4:40 PM, Kamil Dudka wrote:
> On Tuesday, August 22, 2017 1:51:44 PM CEST Michal Novotny wrote:
> > Hey Kamil,
> >
> > On Tue, Aug 22, 2017 at 12:07 PM, Kamil Dudka wrote:
> > > On Tuesday, August 22, 2017 9:04:24 AM CEST Matthias Runge wrote:
> > > > - the ability to dir
On Tuesday, August 22, 2017 1:51:44 PM CEST Michal Novotny wrote:
> Hey Kamil,
>
> On Tue, Aug 22, 2017 at 12:07 PM, Kamil Dudka wrote:
> > On Tuesday, August 22, 2017 9:04:24 AM CEST Matthias Runge wrote:
> > > - the ability to directly upload srpms; that is, one can store spec
> > >
> > > fi
Hey Kamil,
On Tue, Aug 22, 2017 at 12:07 PM, Kamil Dudka wrote:
> On Tuesday, August 22, 2017 9:04:24 AM CEST Matthias Runge wrote:
> > - the ability to directly upload srpms; that is, one can store spec
> > files etc. on the local machine. I'm undecided, if integrating a
> > distgit on copr
Hello Mikolaj,
On Tue, Aug 22, 2017 at 11:29 AM, Mikolaj Izdebski
wrote:
> On 08/22/2017 11:17 AM, Michal Novotny wrote:
> >> - it would be great, if there is a possibility to trigger rebuilds on
> >> dependent packages, like rebuild required packages after ABI bump.
> >>
> >
> > Right, this w
On Tuesday, August 22, 2017 9:04:24 AM CEST Matthias Runge wrote:
> - the ability to directly upload srpms; that is, one can store spec
> files etc. on the local machine. I'm undecided, if integrating a
> distgit on copr would solve any issues or would introduce more, like
> diverging specs.
On 08/22/2017 11:17 AM, Michal Novotny wrote:
>> - it would be great, if there is a possibility to trigger rebuilds on
>> dependent packages, like rebuild required packages after ABI bump.
>>
>
> Right, this would be a nice option. I could imagine this being implemented
> as a configurable fedms
Hello Matthias,
On Tue, Aug 22, 2017 at 9:04 AM, Matthias Runge
wrote:
> On Tue, Aug 22, 2017 at 05:17:56AM +0200, Michal Novotny wrote:
> > Hello,
> >
> > we will have soon a planning meeting that should determine a more
> long-term
> > strategy and bring us to a team agreement on what COPR cur
On Tue, Aug 22, 2017 at 05:17:56AM +0200, Michal Novotny wrote:
> Hello,
>
> we will have soon a planning meeting that should determine a more long-term
> strategy and bring us to a team agreement on what COPR currently is and
> what it should be in half a year or so.
>
> I would like to kindly a
Hello,
we will have soon a planning meeting that should determine a more long-term
strategy and bring us to a team agreement on what COPR currently is and
what it should be in half a year or so.
I would like to kindly ask for some input here on the devel list to find
out what the actual expectati
16 matches
Mail list logo