Re: New Release !

submitted from CLI fail: "invalid request"). clime On Mon, May 30, 2016 at 10:26 AM, Miroslav Suchý <msu...@redhat.com> wrote: > Dne 27.5.2016 v 20:59 Michal Novotny napsal(a): > > a new COPR version was released and put into production today. Apart > from numero

New Release !

Hello, a new COPR version was released and put into production today. Apart from numerous bug fixes, we have also introduced couple of cool new features: - Building RubyGems - Package handling through copr-cli (creating/editing/deleting/listing/fetching) - speeding up Package view - build timeout

Re: New release of Copr

I am not a fan of letting "the old one" die. The whole package building and manipulation interface as well as lately added commands like buildpypi, buildgem, buildtito, buildmock, watch-build were implemented in the clientv1 and with API1. The reason is that the code for API1 and in the original

Tackling COPR service performance issues

Hello guys, we, COPR team, are very sorry for the latest service occasional unavailability. There were several performance issues that we needed to sort out: 1) High memory consumption in API1 on a copr detail - resolved by code optimization 2) Timeouts on search index updating - resolved by

service outage

Hello folks, there will be an outage starting at 2016-07-22 02:00 UTC and will last approximately 4 hours. The reason is OpenStack upgrade on cloud machines where COPR runs. Please see https://fedorahosted.org/fedora-infrastructure/ticket/5410. After that, we will be back :). clime

Re: Please kill my 47 hours old build

Done :-). M. On Thu, Aug 11, 2016 at 7:21 PM, Miro Hrončok wrote: > https://copr.fedorainfracloud.org/coprs/g/python/python33/build/439804/ > > Thanks > -- > Miro Hrončok > -- > Phone: +420777974800 > IRC: mhroncok > ___ >

Re: builld process in trouble ?

re in waiting/starting mode. > > By the way, at least two of my builds have been run twice, when I sent my > e-mail saturday. > > Regards, > Jean-Marc > > Le 11/07/16 à 10:30, Michal Novotny a écrit : > > Hello Jean, > > what kind of trouble? Currently, it seems to work

Re: builld process in trouble ?

Hello Jean, what kind of trouble? Currently, it seems to work well. Sorry that we didn't react earlier by the way. Can you point us to the problematic build? I'll take closer look at it afterwards. Best regards clime On Sat, Jul 9, 2016 at 1:48 PM, Jean-Marc Liger <

New releases of COPR packages

Hello, we have released the following packages today: - python-copr 1.72 - copr-cli 1.53 - copr-frontend 1.97 - copr-backend 1.91 - copr-selinux 1.43 It will take some time until they get into stable repos but if you do not want to wait, you can find the built packages in our official COPR repo

New COPR release

Hey folks, it is our great pleasure to announce that newly released packages have just been deployed on COPR machines, that is: copr-frontend *1.105-1* copr-backend *1.96-1* copr-dist-git *0.24-1* These packages are f25 compatible (including copr-keygen) and offer some new features:

Re: Copr Dependencies for EL

On Wed, Feb 8, 2017 at 10:59 AM, Martin Juhl wrote: > Hi > > I have identified some missing dependencies for building COPR for > CentOS/RHEL... > > Frontend: > > python-flask-whooshee: Is build in the Copr project, but needs to have added > EPEL as a build target, can you do

fedmsg hotfix

Hello, I will deploy fedmsg hotfix tomorrow at 7:30am UTC. I am very sorry for the inconvenience. clime ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org

Re: fedmsg structure change?

On Tue, Jan 24, 2017 at 10:40 PM, Pierre-Yves Chibon <pin...@pingoured.fr> wrote: > On Tue, Jan 24, 2017 at 01:36:59PM +0100, Michal Novotny wrote: > >On Tue, Jan 24, 2017 at 11:44 AM, Pierre-Yves Chibon < > pin...@pingoured.fr> > >wrote: > > > &g

New Release tomorrow

Hello, new COPR version will be deployed tomorrow at 9am UTC. COPR team ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org

Re: upcoming branching

On Mon, Feb 20, 2017 at 8:20 PM, Igor Gnatenko <ignate...@redhat.com> wrote: > On Mon, 2017-02-20 at 16:16 +0100, Michal Novotny wrote: > > Hello, > > > > as soon as branching is done and f26 repo links become available, we > > will > > switch the current

Re: upcoming branching

On Tue, Feb 21, 2017 at 7:56 AM, Pavel Raiskup wrote: > On Tuesday, February 21, 2017 7:18:51 AM CET Igor Gnatenko wrote: > > it depends. if you are planning to do mass-rebuild after branching in > > all copr repos, then I prefer rawhide. If not, I prefer fXY. > > We had

Re: upcoming branching

On Tue, Feb 21, 2017 at 7:18 AM, Igor Gnatenko <ignate...@redhat.com> wrote: > On Mon, 2017-02-20 at 21:28 +0100, Michal Novotny wrote: > > On Mon, Feb 20, 2017 at 8:20 PM, Igor Gnatenko <ignate...@redhat.com> > > wrote: > > > > > On Mon, 2017-

Re: fedmsg structure change?

at 1:36 PM, Michal Novotny <cl...@redhat.com> wrote: > > > On Tue, Jan 24, 2017 at 11:44 AM, Pierre-Yves Chibon <pin...@pingoured.fr> > wrote: > >> On Tue, Jan 24, 2017 at 11:30:33AM +0100, Michal Novotny wrote: >> >Yes, untested changes got into p

New COPR release

Hey folks, updated COPR stack has been just deployed into production. This included several steps: 1) new release of copr-frontend (1.107-1) has been deployed The main features of this release include re-enabling fedora-rawhide as chroot names, compatibility with python2-flask-whooshee-0.4.1-2,

Fwd: New Release!

On Tue, Aug 30, 2016 at 7:43 AM, Pavel Raiskup wrote: > On Tuesday, August 30, 2016 7:39:14 AM CEST Pavel Raiskup wrote: > > Currently it looks like such error-handling is not implemented anyway, > > we drop the build and it is re-submitted after some deadline. > > By "drop"

Re: Mageia chroots enabled

Correction: Mageia-6 and *Mageia-cauldron chroots. Sorry for that! On Wed, Sep 21, 2016 at 1:31 PM, Michal Novotny <cl...@redhat.com> wrote: > Hello all, > > we have just enabled Mageia-6 and Mageia-x86_64 chroots for i586 + x86_64 > archs. So if you want to build something fo

Mageia chroots enabled

Hello all, we have just enabled Mageia-6 and Mageia-x86_64 chroots for i586 + x86_64 archs. So if you want to build something for Mageia (https://www.mageia.org/), please, feel free to try. Best Regards COPR team ___ copr-devel mailing list --

Re: copr-dist-git branch naming and mock names

I think that only real restriction on branch naming is in fedpkg/fedpk-copr (load_rpmdefines function). I think that's the heart of the issue. If you could provide a sane default case for parsing branch_merge variable, then we could adjust everything else (e.g. mock_chroot_name -> branch, branch

Re: Fwd: [Bug 1376844] New: Please start using processes like code-review, etc.

On Wed, Sep 21, 2016 at 3:32 PM, Pavel Raiskup wrote: > > :) Consider that others consume Copr sources ... > > > What is important for me is not important for you and vice versa. > I would say that every commit is important. > > ... and have Copr working, want to have it

| Re: move to pagure

On Mon, Nov 7, 2016 at 3:07 PM, Pavel Raiskup <prais...@redhat.com> wrote: > On Monday, November 7, 2016 1:36:11 PM CET Michal Novotny wrote: > > Hey, > > > > I'd like to ask the community if it's alright to officially move to > pagure. > > I should have

| Re: Build respawing?

Basically, there is a difference in build-time calculation for chroots and builds. For chroot, it is end_time - start_time and for build it is chroot_max_end_time - chroot_min_end_time (in other words, for a build, all its chroots are considered in time calculation). The thing is that your x86_64

| Re: codebase moved to pagure.io

pdated? > > > https://pagure.io/copr/copr/blob/master/f/README.md?text=True#_3 > > > And the fedorahosted should be update as well IMO. > > > > Vít > > > > > Dne 21.10.2016 v 13:00 Michal Novotny napsal(a): > > Hello folks, > > codebase will be now

| Re: tail the logs

This is not yet implemented. I agree, it would be nice. On Tue, Nov 29, 2016 at 4:31 AM, Ryan H. Lewis wrote: > Koji allows us to the the logs more or less as they are generated. Is it > possible to do the same with koji? I have long builds ~30 minutes -- 1 > hour. It is

| planned hotfix deployment for build restarting

Today (11/22) at 4pm UTC, I will apply a hotfix for build restarting. Also, I will attempt to address https://bugzilla.redhat.com/ show_bug.cgi?id=1395582 for ppc64le builders. clime ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To

| Re: Loading changes to an own Copr project

On Thu, Nov 17, 2016 at 11:10 AM, Antonio Trande wrote: > Hi all. > > How can i commit changes to my Copr project without uploading source > code archive every time? > > You want to push changes to copr-dist-git ( http://copr-dist-git.fedorainfracloud.org) without a

| codebase moved to pagure.io

Hello folks, codebase will be now hosted on pagure.io (https://pagure.io/copr/copr). We would like to start working on this platform. Not that Github is bad but I think that pagure.io will be good place as well. COPR team ___ copr-devel mailing list --

| Re: codebase moved to pagure.io

wrote: > Dne 21.10.2016 v 13:00 Michal Novotny napsal(a): > > codebase will be now hosted on pagure.io <http://pagure.io> ( > https://pagure.io/copr/copr). We would like to start > > working on this platform. Not that Github is bad but I think that > pagure.io <

| Re: codebase moved to pagure.io

On Thu, Oct 27, 2016 at 7:56 PM, Pierre-Yves Chibon wrote: > Pagure supports web-hook as well as fedmsg for notifying of an action. > There is also of course the possibility to add COPR as some sort of CI > service > like we have for jenkins but that would be a little more

| Re: codebase moved to pagure.io

On Mon, Oct 31, 2016 at 8:40 AM, Pierre-Yves Chibon wrote: > We used to send more info but had to trim it down due to some massive > commits > that were basically breaking datagrepper (OutOfMemory), but if there is an > use-case I'm fine with expending the amount of

| Re: codebase moved to pagure.io

On Mon, Oct 31, 2016 at 12:05 PM, Pierre-Yves Chibon <pin...@pingoured.fr> wrote: > On Mon, Oct 31, 2016 at 11:59:47AM +0100, Michal Novotny wrote: > >On Mon, Oct 31, 2016 at 8:40 AM, Pierre-Yves Chibon < > pin...@pingoured.fr> > >wrote: > > > &

| Re: Fork "from" or "to" rawhide?

The lighttpd aliases/redirects will be good to keep copr project's baseurls with *rawhide* in it working. You might want to use those. On Mon, Oct 10, 2016 at 5:10 PM, Pavel Raiskup <prais...@redhat.com> wrote: > Hi Michal, > > On Monday, October 10, 2016 4:39:11 PM CEST Micha

Re: COPR chroots additions/deletions

The reason is that the backend_rawhide_to_release command that I used for transition of builds from rawhide to f26 copies only the latest successful builds for each package. Your needed dependency, however, comes from a build 468985 that was marked as failed but still contains (as the only one)

Re: python-novaclient package??

script if that shows anything. 'Inappropriate IOCTL on device' might mean that you try to read/write on tty you do not have access to but not sure if this information will help you in any way. /Martin > > > - Original meddelelse - > Fra: "Michal Novotny" <cl...@re

Re: COPR shows "failed", but in fact build succeeded

There was Gateway Timeout on copr-keygen. The machine was likely overloaded at that time. On Mon, Dec 5, 2016 at 10:58 PM, Igor Gnatenko wrote: > https://copr.fedorainfracloud.org/coprs/rpmsoftwaremanagement/rpm- > gitoverlay-1480969917.509235/build/485123/ > -- > -Igor

Re: python-novaclient package??

On Mon, Dec 5, 2016 at 11:47 AM, Martin Juhl wrote: > Ok... Might have fixed that myself... > > Using the /centos/7.2.1511/cloud/x86_64/openstack-kilo/ it seems to > work... > > Now i'm getting: > > ==> /var/log/copr-backend/vmm.log <== > [2016-12-05 11:15:37,384][ >

Re: failed to post data to frontend

On Mon, Dec 5, 2016 at 1:47 PM, Martin Juhl wrote: > Hi > > I'm getting these errors/warnings: > > ==> /var/log/copr-backend/backend.log <== > [2016-12-05 11:57:15,358][WARNING][backend.main][frontend.py:_ > post_to_frontend_repeatedly:48] failed to post data to frontend,

Re: dist-git is failing to import

On Mon, Dec 5, 2016 at 4:46 PM, Martin Juhl wrote: > When trying to import, dist-git is failing: > > [15:12:20][DEBUG][dist_git.dist_git_importer][dist_git_importer:392] 1. > Try to get task data > [15:12:20][INFO][dist_git.dist_git_importer][dist_git_importer:484] 2. > Task:

| Upcoming release today

Hello, today at 7pm UTC, the latest COPR stack will be deployed into production. clime ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org

Re: COPR chroots additions/deletions

l Novotný wrote: > > > > > > > > > > > > > > > On Sáb, 2016-12-03 at 22:41 +0100, Michal Novotny wrote: > > > > > > > > I built successfully 2 packages for 26 and on 3rd fails [1] with > > > > same > > > > error: > >

Re: please clean deleted builds

All gpgme builds were deleted from sergiomb/kde4for23. I still wonder why they stayed there. On Tue, Mar 28, 2017 at 12:34 PM, Sérgio Basto wrote: > > Hi > in https://copr-be.cloud.fedoraproject.org/results/sergiomb/kde4for23/ > > please delete all gpgme builds > >

Re: copr-cli Upstream URL

Hello Jun, It's located here: https://pagure.io/copr/copr/blob/master/f/cli. The links will be fixed in the next release. Best Regards clime On Wed, Apr 12, 2017 at 6:22 PM, Jun Aruga wrote: > Hello, > > Where is new upstream URL of copr-cli? > I want to see latest source

New Release

Hey folks, yesterday, we have released the latest state of our COPR stack. It contains a _lot_ of new features and even though it's not perfect, it's still pretty damn good. The main feature addition was perhaps support for building modules directly from a modulemd file or from a SCM url by

COPR rawhide repo links

Dear rawhide users, if you have enabled a COPR repo in the last three months (since the beginning of December last year till yesterday), then it points to fedora-$releasever-$basearch. You can reenable it by using `dnf copr enable ` to get .repo file pointing to actual fedora-rawhide chroot in

Re: COPR rawhide repo links

from now on. We will make sure we provide means you will not need to care about branching next time. For COPR team clime > Vít > > > [1] https://copr.fedorainfracloud.org/coprs/vo is ndruch/doublecmd/ > <https://copr.fedorainfracloud.org/coprs/vondruch/doublecmd/> > > Dne

COPR deploy

Hello, we have just deployed copr-frontend 1.117 and copr-dist-git 0.34. The deploy is quite special because the packages' origin is Fedora Infrastructure repositories for the first time and not @copr/copr repo as it used to be. That is because we have switched to deploying COPR only from official

Re: copr-dist-git hotfixes

Hello Richard, On Sun, Jul 16, 2017 at 1:13 AM, Richard Shaw wrote: > Maybe unrelated but I noticed that in the last few builds I did that all > the log entries were entered twice... > > This is probably related to https://github.com/rpm-software-management/mock/issues/73.

New copr-frontend release

Hello, I am sending these release notes also to fedora-devel list (and not just copr-devel list as usually) because they contain information about upcoming Fedora branching and what features COPR provides to move the set of packages from your rawhide chroots into the newly branched ones. We have

Re: New copr-frontend and copr-rpmbuild deploy

es soon for your satisfaction. COPR team On Thu, Jun 29, 2017 at 9:34 PM, Jeandet Alexis < alexis.jean...@member.fsf.org> wrote: > Hi Michal & COPR team, > > Fetching sources from github works now! Thank you :). > I really like COPR. > > Best regards, > Alexis. > L

Re: Mock SCM git repo Name Vs package name

ttps://pagure.io/copr/copr) would help ;). You can e.g. see https://copr.fedorainfracloud.org/coprs/g/mock/mock/ as an example project hosted on Github that uses MockSCM build method. > > Best regards, > Alexis. > Le mardi 27 juin 2017 à 11:13 +0200, Michal Novotny a écrit : > > C

Re: Builders are in pending mode

It should be alright now even though still quite slow. We were hitting open ports limit is now alleviated. New builder spawning could be probably a little bit more aggressive to utilize resources better and also should be faster. We still have have some open slots for new builders but they are not

New copr-frontend and copr-rpmbuild deploy

Hello, we have just deployed the latest upstream version of copr-frontend to fix an issue with invalid quoting of baseurl for an additional repo if it contained '$' symbol. You may check the logs for errors if you use an additonal repos feature. We have also built the latest upstream

Re: repodata directory is not updated after build

Hello, it should be fixed now. Sorry for the problems. clime 2017-04-25 13:39 GMT+02:00 Jean-Marc Liger < jean-marc.li...@parisdescartes.fr>: > Hi, > > Since yesterday, my repodata directories are not updated after each build. > > Regards, > -- > > > > * Jean-Marc LIGER Ingénieur Systèmes et

mock's dual bootstrapping enabled by default for existing copr projects

Hello, while working on another thing, I noticed that when use_bootstrap_container project option was introduced (Wed Jun 14 this year), it was introduced as enabled for existing COPR projects at that time. That was not exactly intended as this feature is experimental. Enabling this option makes

Re: fedora-26-ppc64le fails with Public key for gcc-7.0.1-0.15.fc26.ppc64le.rpm is not installed

Hello Sérgio, this is now fixed. Thank you a lot for your report! clime On Sat, May 6, 2017 at 8:27 PM, Sérgio Basto wrote: > Hi, > > from [1] > DEBUG util.py:439: warning: /var/lib/mock/fedora-26- > ppc64le-mockbuilder-28693/root/var/cache/dnf/fedora- >

New release

Hello, we have just released latest state of COPR server stack. Main changes include: - usage of standalone builder on a builder machine, yet to be officially packaged - custom dist-git branching (for different distros) - dist-git import into separate branches is now only a single import task

Planned outtage

Hello guys, there is planned cloud outage in one hour: https://pagure.io/fedora-infrastructure/issue/6135 COPR team ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org

Re: Mock SCM git repo Name Vs package name

result = func(*args, **kw) > File "/usr/lib/python3.5/site-packages/mockbuild/util.py", line 532, in > do > preexec_fn=preexec, > File "/usr/lib64/python3.5/subprocess.py", line 676, in __init__ > restore_signals, start_new_session) > File "/u

New copr-frontend released

Hello, just a quick update... new copr-frontend (1.110) has been released (and deployed). It contains Gitlab webhooks support (see Settings -> Webhooks in your COPR projects for more info) as new a feature and it also attempts to fix Pagure projects auto-rebuilds. Best regards COPR team

W21 2017 status

COPR: - improved copr-dist-git's performance by reimplementing MockScmProvider - again made Pagure repo auto-rebuilding script more error-prone - implemented Gitlab webhooks - did some brainstorming with Pavel Raiskup - reviewed https://pagure.io/copr/copr/pull-request/11 - released and deployed

Re: please clean deleted builds

Right, that means it wasn't cancelled on builder for some reason. We will look into that this week. Thank you! clime On Sun, May 28, 2017 at 4:41 AM, Sérgio Basto <ser...@serjux.com> wrote: > On Wed, 2017-03-29 at 10:25 +0200, Michal Novotny wrote: > > All gpgme builds we

Re: Mock SCM git repo Name Vs package name

Hello, I am just deploying a new version of copr-dist-git that should fix that particular problem so you can try that. There seems to be a problem later on in building phase but we need to solve it afterwards. clime On Wed, May 31, 2017 at 12:54 AM, Jeandet Alexis < alexis.jean...@member.fsf.org>

Re: Mock SCM git repo Name Vs package name

(name of the package + version). If the command was %autosetup -q, it would work. Are you able to change the name of the directory in the archive at https://github.com/jeandet/vera/archive/master.tar.gz? clime On Wed, May 31, 2017 at 11:59 AM, Michal Novotny <cl...@redhat.com> wrote: > He

Re: 62 packages importing none building?

The importing queue was stuck due to improper error handling in copr-dist-git package. We have deployed a new hotfixed copr-dist-git version that should solve it. Sorry for the problems COPR team On Sun, Jun 4, 2017 at 3:59 PM, Richard Shaw wrote: > Anyone know what's up?

Re: builds failing

This should be now fixed as well. Thank you! COPR On Sat, Jun 10, 2017 at 3:53 PM, Thomas Moschny wrote: > > We have deployed the a version that should solve both the > > problems. Let us know if it works or if it doesn't. > > The *ppc64le builders still seem to fail

Re: "No such file or directory" when building SRPM

Yes, there was an error in the new copr-rpmbuild script that it completely ignored patches (and other files apart from tarball and spec) and it also supported only one tarball reference in source file. I have deployed a new version that should solve the problems. clime On Sat, Jun 10, 2017 at

builds failing

Hello, as it proved the new builder script that we now use was written to simplistically (incorrectly). It ignored patches and supported only one tarball reference. We have deployed the a version that should solve both the problems. Let us know if it works or if it doesn't. Thank you COPR

Re: "No such file or directory" when building SRPM

now, however, try to fully specify the path to conan (i.e. ~/.local/bin/conan). On Sat, Jun 10, 2017 at 5:29 PM, Jonathan Leroy <jonat...@harrycow.fr> wrote: > 2017-06-10 12:31 GMT+02:00 Michal Novotny <cl...@redhat.com>: > > Yes, there was an error in the new

Re: "No such file or directory" when building SRPM

On Wed, Jun 14, 2017 at 10:57 AM, Jonathan Leroy wrote: > 2017-06-12 11:12 GMT+02:00 Jonathan Leroy : > > Thank you Michal. > > I will wait for the new release. > > There is a DNS resolution problem this morning : > > fatal: unable to access

COPR is not working properly

Hello, since Sunday, we have been fighting with an issue on copr-dist-git machine that causes all imports and hence builds fail when it occurs. Apart from corrupted journal logs, we have not been able to find any other possible cause(s). These were cleaned up today and so far the service has been

Re: Mock SCM git repo Name Vs package name

Le mardi 27 juin 2017 à 15:24 +0200, Michal Novotny a écrit : > > Hello, please, see the answer below... > > On Tue, Jun 27, 2017 at 11:41 AM, jeandet <alexis.jean...@member.fsf.org> > wrote: > > Hello Michal, > > Thank you for your help, I'm not a RPM/Mock/Copr

Re: Error 500 : Internal Server Error ('url')

The problem should be fixed now. Please try and let me know. clime On Thu, Oct 5, 2017 at 4:39 PM, Michal Novotny <cl...@redhat.com> wrote: > Hey, > > On Thu, Oct 5, 2017 at 2:56 PM, Miro Hrončok <mhron...@redhat.com> wrote: > > I may have found an issue with copr: &

Re: Error 500 : Internal Server Error ('url')

Hey, On Thu, Oct 5, 2017 at 2:56 PM, Miro Hrončok wrote: I may have found an issue with copr: > > Yes, it's a bug when accessing not-so-new builds that have not-updated build definition in DB. I can fix it manually in DB and in any case, this will be fixed upon next

Re: Counters down

Hello, On Wed, Aug 23, 2017 at 2:32 PM, Michal Novotny <cl...@redhat.com> wrote: > Hello! > > On Wed, Aug 23, 2017 at 2:29 PM, Jean-Marc Liger <jean-marc.liger@ > parisdescartes.fr> wrote: > >> >> Le 22/08/2017 à 11:55, Jean-Marc Liger a écrit : >

Re: New release

Hello Igor! On Fri, Sep 8, 2017 at 9:18 AM, Igor Gnatenko < ignatenkobr...@fedoraproject.org> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Thu, 2017-09-07 at 22:46 +0200, Michal Novotny wrote: > > Hello! > > > > We have just relea

Re: New release

Hey Jean-Marc, On Fri, Sep 8, 2017 at 9:50 AM, Jean-Marc Liger < jean-marc.li...@parisdescartes.fr> wrote: > Hi, > > Le 07/09/2017 à 22:46, Michal Novotny a écrit : > >> Hello! >> >> We have just released new COPR stack. There is one big important change: &

Missing logs for "Attempt to build SRPM have failed." error

Hello, If you encounter this error, you probably also won't get any easy access to the logs about the error :(. We will fix that in the next release. For now, you can access the logs in a slightly more difficult way: They are placed at: https://copr-be.cloud.fedoraproject.org/results/<

Re: New release

Hello Jean-Marc, On Mon, Sep 11, 2017 at 2:00 PM, Jean-Marc Liger < jean-marc.li...@parisdescartes.fr> wrote: > Hi Clime, > Le 07/09/2017 à 22:46, Michal Novotny a écrit : > > Hello! > > We have just released new COPR stack. There is one big important change: > > S

Re: New release

Hello Robert, On Sun, Sep 10, 2017 at 5:35 PM, Robert-André Mauchin wrote: > > Hello! > > > > We have just released new COPR stack. There is one big important change: > > > > SRPMs are now built on builders before they get imported into DistGit. > > > > There will be more to

New release

Hello! We have just released new COPR stack. There is one big important change: SRPMs are now built on builders before they get imported into DistGit. There will be more to follow regarding SRPM generation. Thank you for building on COPR COPR team

Re: CI-style package builds from a Git repository

Hello Florian, yes, it should be possible. I would need to see the build to debug the problem. Thank you clime On Mon, Oct 2, 2017 at 3:28 PM, Florian Weimer wrote: > Is there a way to get Copr to build binary packages directly from a Git > repository? I do not need the

New deploy

Hello, today, we have deployed new copr-frontend 1.120-1, copr-backend 1.103-1, and copr-keygen 1.68-1. Changes in keygen and backend are mainly cosmetic (i.e. spelling fixes) but in frontend, there are quite a few: - fix build stucking with srpm url/upload resubmitted builds - .spec cleanup -

fedora chroot updates

Hello, fedora-24 chroots were removed from COPR and fedora-27 chroots were added. For projects with "Follow Fedora branching" option enabled, the fedora-27 chroots were auto-created in their projects and existing builds from the rawhide chroots were copied there. COPR team

Re: "No such command: builddep." with Fedora Rawhide chroot

The problem with rawhide dnf is described here: https://bugzilla.redhat.com/show_bug.cgi?id=1483342 On Mon, Aug 21, 2017 at 11:14 AM, Pavel Raiskup <prais...@redhat.com> wrote: > On Monday, August 21, 2017 10:14:55 AM CEST Michal Novotny wrote: > > Hello, this might be a change

Re: "No such command: builddep." with Fedora Rawhide chroot

Hello, this might be a change in rawhide dnf-plugins-core (or dnf). Please, if you don't need mock bootstrap feature enabled in your project settings, then you can disable it. That way, host system dnf and dnf-plugins-core will be used. I'll look closely at what causes the problem in the rawhide

Re: Counters down

Hello Jean, do you mean download counters for your repositories? clime On Mon, Aug 21, 2017 at 2:37 PM, Jean-Marc Liger < jean-marc.li...@parisdescartes.fr> wrote: > Hi, > > My counters are down for some weeks now. > > Regards, > > Jean-Marc > ___ >

Re: build process doesn't work for me

Hello Jean, no problem at all. Glad you figured it out. On Fri, Aug 25, 2017 at 7:06 PM, Jean-Marc Liger < jean-marc.li...@parisdescartes.fr> wrote: > > > Le 25/08/2017 à 17:03, Jean-Marc Liger a écrit : > > Le 25/08/2017 à 14:07, Jean-Marc Liger a écrit : > > Hello, > > All my builds have a

Re: Getting error "Could not parse *.spec" on copr build

status there. Thank you clime On Fri, Sep 1, 2017 at 11:31 PM, Robbi Nespu <robbine...@fedoraproject.org> wrote: > Thank you, Where I can see bug status regarding this issue? I can't find > it on bugzilla. > > On Fri, Sep 1, 2017 at 3:42 AM, Michal Novotny <cl...@redhat.com

Re: ppc64le still in pending mode

Hello Jean! On Thu, Oct 19, 2017 at 9:58 AM, Jean-Marc Liger < jean-marc.li...@parisdescartes.fr> wrote: > Hello, > > It seems that ppc64le builders are stuck in pending mode. > > Thank you for the info! It should be fixed now. > Regards, > > Jean-Marc > >

New Deploy

Hello, we have just deployed the latest COPR stack. Apart from a few bugfixes, there is one important update: SCM source types were finally unified so now there is only one "SCM" tab. You can also use copr command-line client (copr-cli) to build for any Github/Gitlab/DistGit repo. See `copr-cli

COPR: usage of http:// in python client

Hello, we have found out that http://copr.fedoraproject.org was used as default API endpoint if no copr_url was specified for CoprClient initialization. This is now fixed in the latest version of python-copr (python-copr-1.84) and we recommend updating to that version. Also we have decided to

Re: long waiting times for COPR jobs

Hello Jean-Marc, answer is below... On Tue, Nov 28, 2017 at 11:20 AM, Jean-Marc Liger < jean-marc.li...@parisdescartes.fr> wrote: > Hi Clime, > Le 03/11/2017 à 06:39, Michal Novotny a écrit : > > Hey, > > On Wed, Nov 1, 2017 at 3:42 PM, Michal Novotny <cl...@re

Re: is COPR down?

COPR is back now. Sorry for the problems. We get high load peaks at times. clime On Mon, Dec 4, 2017 at 7:05 PM, David Shea wrote: > Connection is timing out connecting to copr.fedorainfracloud.org. Is > there an ETA on when it will come back? >

COPR outage at 1am UTC

Hello, today there will be a COPR outage lasting approximately for 1 hour starting at 1 a.m. UTC. We will be upgrading most of the machines to the latest released Fedora version. COPR Team ___ copr-devel mailing list --

Re: COPR outage at 1am UTC

I am very sorry. I meant 1pm UTC today. Best regrads On behalf of COPR team clime On Mon, Dec 18, 2017 at 10:03 AM, Michal Novotny <cl...@redhat.com> wrote: > Hello, > > today there will be a COPR outage lasting approximately for 1 hour > starting at 1 a.m. UTC. We will

long waiting times for COPR jobs

Hello, lately, COPR pending job queues are holding jobs for pretty long time (even hours). This is a buggy behaviour and we will be doing our best to fix this issue in the following days. Thank your for your patience COPR team ___ copr-devel mailing

  1   2   >