Re: Copr in 2020 and outlook for 2021

2021-02-15 Thread Ken Dreyer
On Sat, Feb 13, 2021 at 3:06 PM Ken Dreyer wrote: > > On Mon, Jan 4, 2021 at 9:52 AM Miroslav Suchý wrote: > > * Contribute to fedpkg/koji to have machine-readable output. > > There is a "--json" argument to "koji call", and that produces > machine-readable output for individual Koji RPCs. > > I

Re: Copr in 2020 and outlook for 2021

2021-02-13 Thread Ken Dreyer
On Mon, Jan 4, 2021 at 9:52 AM Miroslav Suchý wrote: > * Contribute to fedpkg/koji to have machine-readable output. There is a "--json" argument to "koji call", and that produces machine-readable output for individual Koji RPCs. It would be really nice if rpkg had something similar, or even an

Re: Copr in 2020 and outlook for 2021

2021-01-04 Thread Miro Hrončok
On 04. 01. 21 20:53, Miro Hrončok wrote: On 04. 01. 21 20:48, Miroslav Suchý wrote: Dne 04. 01. 21 v 20:14 Miro Hrončok napsal(a): Is there any chance we could vote for GitHub Actions enablement instead of Travis? Currently we run a Fedora Docker image on top of the Ubuntu host, which is less t

Re: Copr in 2020 and outlook for 2021

2021-01-04 Thread Miro Hrončok
On 04. 01. 21 20:48, Miroslav Suchý wrote: Dne 04. 01. 21 v 20:14 Miro Hrončok napsal(a): Is there any chance we could vote for GitHub Actions enablement instead of Travis? Currently we run a Fedora Docker image on top of the Ubuntu host, which is less than ideal in some cases (e.g., filesystem

Re: Copr in 2020 and outlook for 2021

2021-01-04 Thread Miroslav Suchý
Dne 04. 01. 21 v 20:14 Miro Hrončok napsal(a): >> Is there any >> chance we could vote for GitHub Actions enablement instead of Travis? >> Currently we run a Fedora Docker image on top of the Ubuntu host, >> which is less than ideal in some cases (e.g., filesystem package >> upgrades...). > > I wa

Re: Copr in 2020 and outlook for 2021

2021-01-04 Thread Miroslav Suchý
Dne 04. 01. 21 v 20:36 Dan Čermák napsal(a): > Is it intentional that google asks me to sign in? I don't actually have > a google account. Yes. It is intentional. The motivation is that you can change your vote later. If you do not have google account then just write me an email. I will add it to

Re: Copr in 2020 and outlook for 2021

2021-01-04 Thread Dan Čermák
Hi, Miroslav Suchý writes: > Let me sum up what we - the Copr team - did in 2020: > > * We enabled CDN for repos. https://fedora-copr.github.io/posts/copr-cdn > > * We enabled runtime dependecies on repositories > https://fedora-copr.github.io/posts/runtime-dependencies > > * We migrated all

Re: Copr in 2020 and outlook for 2021

2021-01-04 Thread Miro Hrončok
On 04. 01. 21 18:40, Alexander Scheel wrote: * Native support for Fedora in Travis. Travis has made a lot of changes to how OSS projects can use it, and (IMO) burnt a lot of good will in the community. All of our upstream projects ended up moving off it and onto GitHub Actions. Is there any ch

Re: Copr in 2020 and outlook for 2021

2021-01-04 Thread Alexander Scheel
Congrats! I can say I've used several of these features and they work well, thanks for your team's work! One query inline... :) On Mon, Jan 4, 2021 at 11:53 AM Miroslav Suchý wrote: > > Let me sum up what we - the Copr team - did in 2020: > > * We enabled CDN for repos. https://fedora-copr.git

Copr in 2020 and outlook for 2021

2021-01-04 Thread Miroslav Suchý
Let me sum up what we - the Copr team - did in 2020: * We enabled CDN for repos. https://fedora-copr.github.io/posts/copr-cdn * We enabled runtime dependecies on repositories https://fedora-copr.github.io/posts/runtime-dependencies * We migrated all our servers from PHX datacenter to AWS. Wi