EPEL6, Fedora ELN, and Mageia Cauldron

[Jakub Kadlcik]

Hello,
I did a small cleanup of old/broken chroots, so just that everybody knows:

- I marked epel-6-i386 and epel-6-x86_64 as EOL (see previous email by
msuchy)
- I marked fedora-eln-i386 as EOL
- I renamed mageia-cauldron-i586 chroot to mageia-cauldron-i686

Relevant tickets:

[1] https://github.com/fedora-copr/copr/issues/3357
[2] https://github.com/fedora-copr/copr/issues/3354
[3] https://github.com/fedora-copr/copr/issues/3339

Jakub
-- 
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Outage: Upgrade of Copr servers - 2024-05-22 09:00 UTC

[Jakub Kadlcik]

The outage is over, everything should work as expected.
Release notes:
https://docs.pagure.org/copr.copr/release-notes/2024-05-22.html

Happy building

On Mon, May 20, 2024 at 8:49 PM Jakub Kadlcik  wrote:

> Hello,
>
> There will be an outage starting at:
>
> $ date --date '2024-05-22 09:00 UTC'
>
> The outage will last approximately 3 hours. The copr-backend storage (copr
> build results) will stay mostly online during this outage but some
> downtime is expected.
>
> Reason for outage:
> We're updating copr packages to the new versions which will bring new
> features and bugfixes.
>
> Affected Services:
> copr-frontend - https://copr.fedorainfracloud.org
> copr-backend - https://copr-be.cloud.fedoraproject.org/
>
> Ticket:
> https://pagure.io/fedora-infrastructure/issue/11932
>
> Contact persons:
> @frostyx / @praiskup / @nikromen
>
> Please join Fedora Build System Matrix channel
> https://matrix.to/#/#buildsys:fedoraproject.org
> or comment on this ticket.
>
--
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Outage: Upgrade of Copr servers - 2024-05-22 09:00 UTC

[Jakub Kadlcik]

Hello,

There will be an outage starting at:

$ date --date '2024-05-22 09:00 UTC'

The outage will last approximately 3 hours. The copr-backend storage (copr
build results) will stay mostly online during this outage but some downtime
is expected.

Reason for outage:
We're updating copr packages to the new versions which will bring new
features and bugfixes.

Affected Services:
copr-frontend - https://copr.fedorainfracloud.org
copr-backend - https://copr-be.cloud.fedoraproject.org/

Ticket:
https://pagure.io/fedora-infrastructure/issue/11932

Contact persons:
@frostyx / @praiskup / @nikromen

Please join Fedora Build System Matrix channel
https://matrix.to/#/#buildsys:fedoraproject.org
or comment on this ticket.
--
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

CentOS Stream 10 chroots added to Copr

[Jakub Kadlcik]

Hello,
we added Centos Stream 10 chroots to Copr. These are now available:

- centos-stream-10-x86_64
- centos-stream-10-ppc64le
- centos-stream-10-aarch64
- centos-stream-10-s390x

Jakub
--
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

User SSH access to Copr builders

[Jakub Kadlcik]

Hello,
this may be a useful feature for many people, so I wanted to announce it
separately.

Debugging failed Copr builds became much easier with the last release.
https://docs.pagure.org/copr.copr/release-notes/2024-03-07.html

You can now enable SSH access to the builder, connect using your pubkey,
and run any commands you need to debug the issue. Everything is explained
in my blog post.
https://frostyx.cz/posts/ssh-access-to-copr-builders

Jakub
--
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Fedora Review feature in Copr and Fedora Review Service work again

[Jakub Kadlcik]

Hello fellow package maintainers,
we had multiple reports over the last weeks that the fedora-review feature
in Copr produces empty review.txt templates for F40 and Fedora Rawhide. And
as a consequence the Fedora Review Service points to empty review.txt files.

The issue is in the fedora-review tool and it is related to the migration
to DNF5 in new Fedora versions. I am proposing the following fix
https://pagure.io/FedoraReview/pull-request/513 but I decided not to wait
for it to get merged and released.

I applied the proposed patch on Copr builders so everything should work as
expected now. My apologies once again for the downtime.

Jakub
--
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Fedora 40 chroots branched in Copr

[Jakub Kadlcik]

Hello,
we branched Fedora 40 from Rawhide chroots in Copr. The following are now
available:

- fedora-40-aarch64
- fedora-40-i386
- fedora-40-ppc64le
- fedora-40-s390x
- fedora-40-x86_64

Jakub
--
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Copr builders updated to Fedora 39

[Jakub Kadlcik]

Hello package maintainers,

Copr builders have been updated from Fedora 38 to Fedora 39 today.
Everything should work as expected, so if you experience any errors or
strange behavior, please let us know.

Jakub
--
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: builds stucked in starting mode since 7 hours

[Jakub Kadlcik]

I've seen this email in held messages and accepted it but I think an error
was made somewhere and this is probably a duplicate from Thu, Sep 28

Jakub

On Fri, Dec 1, 2023 at 4:36 PM Jean-Marc Liger 
wrote:

> Hi all,
>
> My builds are stucked in starting mode since 7 hours, are we back to
> early (and lovely) years of COPR 😉 ?
>
> Jean-Marc
> --
> ___
> copr-devel mailing list -- copr-devel@lists.fedorahosted.org
> To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>
--
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: PyPI build failing on copr but works locally on f38

[Jakub Kadlcik]

Hello Barry,
thank you for debugging the issue.

Looking at the Copr logs from your build, I don't have an idea why it
failed either. My guess is that you encountered some temporary
infrastructure issue.
I tried to build the package in Copr and it worked for me
https://copr.fedorainfracloud.org/coprs/frostyx/test-pypi-config-path/build/6489299/
Can you please try resubmitting the build in your project?

Jakub



On Tue, Oct 3, 2023 at 10:14 PM Barry Scott  wrote:

> I'm trying to package my PyPI config-path package.
>
> Its failing to build:
> https://copr.fedorainfracloud.org/coprs/barryascott/tools/build/6487785/
>
> The log
>
> https://download.copr.fedorainfracloud.org/results/barryascott/tools/srpm-builds/06487785/builder-live.log.gz
> I see no error message that is actionable only report of failure.
> The log tells me that I can do the build locally.
>
> I have followed these steps to check the build locally on my up to date
> f38:
>
> sudo dnf install copr-rpmbuild
>
> /usr/bin/copr-rpmbuild --verbose --drop-resultdir --srpm --task-url
> https://copr.fedorainfracloud.org/backend/get-srpm-build-task/6487785
>
> I also needed to sudo dnf install pyp2spec
>
> Then I needed to set /etc/mock/default.cfg to point to an existing cfg,
> it was pointing to fedoara-35-x86_64.cfg
> I set it to fedora-38-x86_64.cfg.
>
> This build completes without error and I have a .src.rpm created.
>
> I also set /etc/mock/default.cfg to point to fedora-rawhide-x86_64 as
> the copr build log suggests
> that is what  using and the build succeeded as well.
>
> I can then use mock to build the binary rpm:
>
> mock -r fedora-38-x86_64 --rebuild
> /var/lib/copr-rpmbuild/results/python-config-path-1.0.5-1.src.rpm
>
> Which creates:
>
> $ ll /var/lib/mock/fedora-38-x86_64/result
> total 368
> -rw-rw-r--. 1 barry  55899 2023-10-03 21:00:35 build.log
> -rw-rw-r--. 1 barry   3454 2023-10-03 21:00:14 hw_info.log
> -rw-rw-r--. 1 barry  15194 2023-10-03 21:00:24 installed_pkgs.log
> -rw-r--r--. 1 barry  19114 2023-10-03 21:00:35
> python3-config-path-1.0.5-1.fc38.noarch.rpm
> -rw-r--r--. 1 barry  29486 2023-10-03 21:00:35
> python-config-path-1.0.5-1.fc38.src.rpm
> -rw-rw-r--. 1 barry 238389 2023-10-03 21:00:35 root.log
> -rw-rw-r--. 1 barry   1414 2023-10-03 21:00:35 state.log
>
> Why does it fail at copr.fedorainfracloud.org but work locally?
>
> Barry
>
> ___
> copr-devel mailing list -- copr-devel@lists.fedorahosted.org
> To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: builds stucked in starting mode since 7 hours

[Jakub Kadlcik]

Hello,

> are we back to early (and lovely) years of COPR 😉 ?

Yeah, we felt a bit nostalgic :-)

Sorry about the downtime, we had issues with spawning new builders because
the subscription-manager was timeouting and it was the middle of the night
here. Mirek already resolved it. There is a bit of a queue but builds are
running again.

Jakub

On Thu, Sep 28, 2023 at 8:00 AM Jean-Marc Liger <
jean-marc.li...@parisdescartes.fr> wrote:

> Hi all,
>
> My builds are stucked in starting mode since 7 hours, are we back to
> early (and lovely) years of COPR 😉 ?
>
> Jean-Marc
>
> ___
> copr-devel mailing list -- copr-devel@lists.fedorahosted.org
> To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: OUTAGE: Fedora Copr - updating to a new August 2023 version

[Jakub Kadlcik]

Hello,
Copr repositories were unavailable for ~10 minutes during the outage
because we wanted to fully update all installed packages and reboot the
servers. We are sorry for any inconvenience caused by this.

Everything should be up and running now. If you are interested, check out
the release notes
https://docs.pagure.org/copr.copr/release-notes/2023-08-16.html

Happy building,
Jakub

On Fri, Aug 11, 2023 at 5:43 PM Pavel Raiskup  wrote:

> There will be an outage starting at
>
> date --date "2023-08-16 12:30 UTC"
>
> it will last approximately 2 hours. The build queue processing will be
> stopped. During the outage time, we expect a very short downtime for the
> DNF package storage (== copr-backend, download.copr.f.o, less than 10
> minutes).
>
> Reason for outage:
> We will update the infrastructure machines to the latest packages that
> are currently being developed.
>
> Affected Services:
> https://copr.fedorainfracloud.org/
> https://download.copr.fedorainfracloud.org/results/
>
> Fedora Infra ticket:
> https://pagure.io/fedora-infrastructure/issue/11468
>
> Upstream ticket:
> https://github.com/fedora-copr/copr/issues/2824
>
> Please join #fedora-buildsys, #fedora-admin or #fedora-noc on
> irc.libera.chat or add comments to this ticket.
>
> Copr Team
>
>
> ___
> copr-devel mailing list -- copr-devel@lists.fedorahosted.org
> To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Outage: Upgrade of Copr servers - 2023-05-25 10:00 UTC

[Jakub Kadlcik]

Release notes: https://docs.pagure.org/copr.copr/release-notes/2023-05-25.html

Jakub

On Thu, May 25, 2023 at 1:39 PM Jakub Kadlcik  wrote:
>
> Hello,
> the outage is over. I'll send the release notes in a follow-up email.
>
> Jakub
>
> On Mon, May 22, 2023 at 10:54 PM Jakub Kadlcik  wrote:
> >
> > Hello,
> >
> > There will be an outage starting at:
> >
> > $ date --date '2023-05-25 10:00 UTC'
> >
> > The outage will last approximately 3 hours. The copr-backend storage (copr
> > build results) will stay mostly online during this outage but some
> > downtime is expected.
> >
> > Reason for outage:
> > We're updating copr packages to the new versions which will bring new
> > features and bugfixes.
> >
> > Affected Services:
> > copr-frontend - https://copr.fedorainfracloud.org
> > copr-backend - https://copr-be.cloud.fedoraproject.org/
> >
> > Contact persons:
> > @frostyx / @praiskup / @nikromen
> >
> > Please join #fedora-admin in irc.libera.chat or add comments to the ticket 
> > for
> > this outage above.
> >
> > Jakub
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Outage: Upgrade of Copr servers - 2023-05-25 10:00 UTC

[Jakub Kadlcik]

Hello,
the outage is over. I'll send the release notes in a follow-up email.

Jakub

On Mon, May 22, 2023 at 10:54 PM Jakub Kadlcik  wrote:
>
> Hello,
>
> There will be an outage starting at:
>
> $ date --date '2023-05-25 10:00 UTC'
>
> The outage will last approximately 3 hours. The copr-backend storage (copr
> build results) will stay mostly online during this outage but some
> downtime is expected.
>
> Reason for outage:
> We're updating copr packages to the new versions which will bring new
> features and bugfixes.
>
> Affected Services:
> copr-frontend - https://copr.fedorainfracloud.org
> copr-backend - https://copr-be.cloud.fedoraproject.org/
>
> Contact persons:
> @frostyx / @praiskup / @nikromen
>
> Please join #fedora-admin in irc.libera.chat or add comments to the ticket for
> this outage above.
>
> Jakub
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Outage: Upgrade of Copr servers - 2023-05-25 10:00 UTC

[Jakub Kadlcik]

Hello,

There will be an outage starting at:

$ date --date '2023-05-25 10:00 UTC'

The outage will last approximately 3 hours. The copr-backend storage (copr
build results) will stay mostly online during this outage but some
downtime is expected.

Reason for outage:
We're updating copr packages to the new versions which will bring new
features and bugfixes.

Affected Services:
copr-frontend - https://copr.fedorainfracloud.org
copr-backend - https://copr-be.cloud.fedoraproject.org/

Contact persons:
@frostyx / @praiskup / @nikromen

Please join #fedora-admin in irc.libera.chat or add comments to the ticket for
this outage above.

Jakub
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: PPC64LE problems?

[Jakub Kadlcik]

Hello Steven,
today I also noticed https://bugzilla.redhat.com/show_bug.cgi?id=2152305

We will investigate.

Jakub

On Sat, Dec 10, 2022 at 4:45 PM Steven A. Falco  wrote:
>
> The nightly Copr builds for KiCad are failing on the ppc64le builders [1].
>
> Is this a known problem?  It looks like there has been an issue for the past 
> 3 days or so [2].
>
> Steve
>
> [1] https://copr.fedorainfracloud.org/coprs/g/kicad/kicad/build/5119571/
> [2] https://copr.fedorainfracloud.org/coprs/g/kicad/kicad/builds/
> ___
> copr-devel mailing list -- copr-devel@lists.fedorahosted.org
> To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
> Do not reply to spam, report it: 
> https://pagure.io/fedora-infrastructure/new_issue
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Copr OpenID login should work now

[Jakub Kadlcik]

Hello,
as many of you noticed, we had a problem with login failing with "504
gateway timeout" error for the last couple of days.

I am sorry it took that long to fix, it wasn't easy for me to pinpoint
what exactly is wrong. Anyway, the login should work now. Please let
me know if not.

If you are interested, details can be found here
https://github.com/fedora-copr/copr/issues/2418#issuecomment-1341394581

Jakub
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Outage: Upgrade of Copr servers - 2022-11-28 12:00 UTC

[Jakub Kadlcik]

Hello,
the release notes can be found here:
https://docs.pagure.org/copr.copr/release-notes/2022-11-28.html

The following day we did another (mini) release, focused entirely on
bug fixing. Release notes here:
https://docs.pagure.org/copr.copr/release-notes/2022-11-30.html

Jakub

On Mon, Nov 28, 2022 at 10:44 PM Pavel Raiskup  wrote:
>
>  aaand finally this long outage is over.  This wasn't ideal, sorry for
> any inconveniences.  There were some PEBKAC problems while migrating the
> storage to a new F37 instance, some signature problems (a few builds
> failed because of sign error, please resubmit them) and some failed to
> import (resubmit as well).
>
> Otherwise, we are finally fully on F37 (builders and infrastructure) and
> everything appears to be working.  It was a long day so we'll continue
> tomorrow with remaining stuff, e.g. sending updated cli packages and providing
> release notes.
>
> Happy building.
> Copr Team
>
> On neděle 27. listopadu 2022 2:15:28 CET Jakub Kadlčík wrote:
> >
> > frostyx reported a new issue against the project: `fedora-infrastructure` 
> > that you are following:
> > ``
> > There will be an outage starting at:
> >
> > ```
> > $ date --date '2022-11-28 13:30 UTC'
> > ```
> >
> > The outage will last approximately 3 hours. The copr-backend storage (copr
> > build results) will stay mostly online during this outage but some downtime 
> > is expected.
> >
> > Reason for outage:
> > We're updating copr packages to the new versions which will bring new
> > features and bugfixes. We are also upgrading our servers to F37.
> >
> > Affected Services:
> > copr-frontend - https://copr.fedorainfracloud.org
> > copr-backend - https://copr-be.cloud.fedoraproject.org/
> >
> > Contact persons:
> > @frostyx / @praiskup / @nikromen
> >
> > Please join #fedora-admin in irc.libera.chat or add comments to the ticket 
> > for
> > this outage above.
> > ``
> >
> > To reply, visit the link below or just reply to this email
> > https://pagure.io/fedora-infrastructure/issue/11011
> >
>
>
>
> ___
> copr-devel mailing list -- copr-devel@lists.fedorahosted.org
> To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
> Do not reply to spam, report it: 
> https://pagure.io/fedora-infrastructure/new_issue
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Repository statistics - number of downloads

[Jakub Kadlcik]

Hello Tomas,

> ideally list of countries of the clients that downloaded it.

_Unfortunately_, neither Copr nor the official Fedora repositories
have any such statistics.
On one hand, it would be nice to know how popular our packages are,
and therefore be able to pay them an adequate amount of time. But on
the other, we don't collect any tracking information about our users.

> I'm interested particularly in statistics of one package - number of downloads

At this moment we don't save any per-package download numbers, only
per-repository. So basically there aren't any numbers other than what
is being displayed in a project overview.
Technically, we should be able to implement this feature, so you can
create a RFE at https://pagure.io/copr/copr/issues but I can't promise
any ETA.

Jakub

On Tue, Nov 1, 2022 at 1:09 PM Tomas Cejka  wrote:
>
> Hello everyone,
> I'd like to ask about statistics at https://copr.fedorainfracloud.org/.
> I can see some statistics on number of downloads in the project overview page 
> https://copr.fedorainfracloud.org/coprs/g///
> However, is there some API or some archive to retrieve some long term and 
> ideally more detailed statistics?
>
> I'm interested particularly in statistics of one package - number of 
> downloads and ideally list of countries of the clients that downloaded it.
> Thank you for replies.
> Best Regards
> Tomas Cejka
> ___
> copr-devel mailing list -- copr-devel@lists.fedorahosted.org
> To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
> Do not reply to spam, report it: 
> https://pagure.io/fedora-infrastructure/new_issue
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: reporting a a very old bug

[Jakub Kadlcik]

Hello Sérgio,
it sounds to me like this CDN-related phenomenon
https://docs.pagure.org/copr.copr/user_documentation.html#build-succeeded-but-i-don-t-see-the-built-results

What do you think?
Jakub

On Mon, Oct 24, 2022 at 3:54 PM Sérgio Basto  wrote:
>
> On Mon, 2022-10-24 at 15:23 +0200, Pavel Raiskup wrote:
> > Hello Sérgio, thank you for the question!
> >
> > On Sunday, October 23, 2022 5:55:05 AM CEST Sérgio Basto wrote:
> > > The bug is simply to report, I found it some months ago it with
> > > help of
> > > FrostyX IIRC, after install my own corp build in a laptop .
> >
> > is this a local-only behavior?  I'm getting confused.
>
> No, I just mention my own copr server because also happened there ,
> IIRC and because I could do better debug. On other hand also seems to
> be a problem that can be reproduce in other environment.
> Can be related with lighttpd .
>
> >
> > > The bug is after web page of results show the firsts results, the
> > > web
> > > page is cached and is never updated again.
> >
> > The behavior is documented here:
> > https://docs.pagure.org/copr.copr/user_documentation.html#build-succeeded-but-i-don-t-see-the-built-results
> >
> > But this only ever happens on download.copr.* page, because it is
> > cached through
> > AWS CloudFront.  This is not what is happening on your local machine!
> >
> > > While new files of log are accessible the web page doesn't show it
> > > , this
> > > happens to me a lot when I'm looking at builder-live.log.gz file
> > > while
> > > building is happening .
> >
> > Sure, the compressed file doesn't exist while build is done.  We
> > "stream" the
> > live log from backend, and once the bulid finishes we compress it.
> > Which
> > basically means that 'builder-live.log' is renamed to 'builder-
> > live.log.gz'.
> >
> > Frontend knows about this, so it provides a valid log URL.  Later, we
> > have a
> > lighttpd-based redirect from '*.log' to '*.log.gz' when the '.log'
> > file doesn't
> > exist.
> >
> > Certainly you can not download the compressed when it doesn't exist
> > yet.
> >
> > > For example
> > > https://download.copr.fedorainfracloud.org/results/sergiomb/vboxfor23/fedora-36-x86_64/04962643-kBuild/
> > > doesn't show any build.log.gz and build.log.gz is there in the same
> > > place ase usual
> > > https://download.copr.fedorainfracloud.org/results/sergiomb/vboxfor23/fedora-36-x86_64/04962643-kBuild/build.log.gz
> >
> > This doesn't seem related to your local machine use-case?  Here
> > continues my
> > confusion.
> >
> > Pavel
> >
> > >
> > > Thanks ,
> > > --
> > > Sérgio M. B.
> > > ___
> > > copr-devel mailing list -- copr-devel@lists.fedorahosted.org
> > > To unsubscribe send an email to
> > > copr-devel-le...@lists.fedorahosted.org
> > > Fedora Code of Conduct:
> > > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > > List Guidelines:
> > > https://fedoraproject.org/wiki/Mailing_list_guidelines
> > > List Archives:
> > > https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
> > > Do not reply to spam, report it:
> > > https://pagure.io/fedora-infrastructure/new_issue
> > >
> >
> >
> >
> >
>
> --
> Sérgio M. B.
> ___
> copr-devel mailing list -- copr-devel@lists.fedorahosted.org
> To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
> Do not reply to spam, report it: 
> https://pagure.io/fedora-infrastructure/new_issue
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Inconsistency of bash behaviour on fedora aarch64 and x86_64 images

[Jakub Kadlcik]

Hello TommyLike,
a disclaimer first - I have never tried to run the Copr containers on
an arm architecture, and I am not really a bash person. But

if [ ! -w $REPODIR ] ; then

Checks if a file (or I guess a directory) is writable. Are you sure
you have the correct permissions for $REPODIR ?

Jakub

On Mon, Sep 5, 2022 at 4:59 PM TommyLike Hu  wrote:
>
> Hey COPR Developers,
> Recently, I am trying to deploy COPR containers on an arm instance, 
> except for the base image and resalloc pool tag issues, I also found there is 
> a strange thing on bash command, check this code from dist-git [1] below:
> ```
> if [ ! -w $REPODIR ] ; then
> echo "ERROR: You can not write to $REPODIR"
> echo "ERROR: You can not create repos"
> exit -1
> fi
> ```
> This would always fail in an aarch64 container which uses the identical 
> dockerfile as the x86 ones.
> ```
>
> FROM registry.fedoraproject.org/fedora:35
> MAINTAINER copr-devel@lists.fedorahosted.org
>
> ```
> Could this be a fedora issue? Considering I tried fedora 35/36/37 which all 
> failed.
>
>
> [1]: 
> https://github.com/release-engineering/dist-git/blob/738dc51b8dff6f06a3d4be5f0f480aebf36b1480/scripts/dist-git/setup_git_package#L72
>
> ___
> copr-devel mailing list -- copr-devel@lists.fedorahosted.org
> To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
> Do not reply to spam, report it: 
> https://pagure.io/fedora-infrastructure/new_issue
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Suggestion: Make it obvious where the build logs?

[Jakub Kadlcik]

> Yes that will work, but the Logs in the results section do not link to the
> build.log.gz that contains the errors from rpmbuild.

You are right that build.log.gz isn't linked there, but
builder-live.log.gz is. In the majority of cases, the relevant error
can be found there. I think it should be the case for your build as
well, I can see some ModuleNotFoundError: No module named 'ply'
traceback.

Jakub

On Thu, Sep 1, 2022 at 7:16 PM Barry Scott  wrote:
>
>
>
> > On 30 Aug 2022, at 23:08, Jakub Kadlcik  wrote:
> >
> > Hello Barry,
> > thank you for the feedback.
> >
> >> Maybe make "See logs for more details." link logs to the chroot?
> >
> > That could work when the build is submitted to only one chroot. But
> > usually, a build is submitted into many chroots, and if more of them
> > fail, what would we link then?
> >
> > The results table, where chroot names are, contains also a Logs column
> > with links to logs for each of the chroots. So maybe just rewording
> > the "Build failed. See logs for more details." to say something like
> > "Build failed. For more information see logs in the results section"?
>
> Yes that will work, but the Logs in the results section do not link to the
> build.log.gz that contains the errors from rpmbuild.
>
> I guess its easy enough to also all build.log.gz to the results section.
>
> I would put build.log.gz as the first log in the list on the basis that its
> likely to be the one most people need to read. Or is that just my use case?
>
> Barry
>
>
>
> >
> > Jakub
> >
> > On Fri, Aug 26, 2022 at 5:26 PM Barry Scott  wrote:
> >>
> >> I'm looking at this page:
> >>
> >> https://copr.fedorainfracloud.org/coprs/barryascott/python-qt6/build/4769202/
> >>
> >> Status: failed - Build failed. See logs for more details.
> >>
> >> I do not see an obvious link to the "logs" that it is telling to me view.
> >>
> >> After enough clicking I figured out that its in the chroot that I need to 
> >> look.
> >>
> >> Maybe make "See logs for more details." link logs to the chroot?
> >>
> >> Barry
> >> ___
> >> copr-devel mailing list -- copr-devel@lists.fedorahosted.org
> >> To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
> >> Fedora Code of Conduct: 
> >> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> >> List Archives: 
> >> https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
> >> Do not reply to spam, report it: 
> >> https://pagure.io/fedora-infrastructure/new_issue
> > ___
> > copr-devel mailing list -- copr-devel@lists.fedorahosted.org
> > To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
> > Fedora Code of Conduct: 
> > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives: 
> > https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
> > Do not reply to spam, report it: 
> > https://pagure.io/fedora-infrastructure/new_issue
> ___
> copr-devel mailing list -- copr-devel@lists.fedorahosted.org
> To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
> Do not reply to spam, report it: 
> https://pagure.io/fedora-infrastructure/new_issue
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Running COPR on kubernetes cluster?

[Jakub Kadlcik]

Hello,

>  it always display "No repositories found" which is incorrect

You are right. It can be fixed by editing /etc/cgitrc in the
copr_distgit-httpd_1 container and adding the following line to the
end:

scan-path=/var/lib/dist-git/git

Jakub

On Thu, Sep 1, 2022 at 10:32 AM TommyLike Hu  wrote:
>
> Ha, here comes the problem. with the installation of COPR cluster via 
> command: "docker-compose up", everything looks good, and I can upload srpm 
> and build my version of rpm package successfully, but there is one issue that 
> when browsing git-dist http pages(http://git-dist-http-hostname:port/cgit), 
> it always display "No repositories found" which is incorrect, maybe there is 
> some configuration issue in compose yaml?
>
>
>
> On Thu, Sep 1, 2022 at 9:24 AM TommyLike Hu  wrote:
>>
>> Thanks, The cluster works well in the way docker composing, Now I am 
>> learning COPR, I also would like to have a try if this PR gets merged and 
>> introduce a kubernetes version.
>>
>> On Wed, Aug 31, 2022 at 4:22 AM Jakub Kadlcik  wrote:
>>>
>>> Hello,
>>> I hope you found the blog post helpful.
>>>
>>> There is also an open pull request allowing to run Copr in OpenShift
>>> https://pagure.io/copr/copr/pull-request/2193
>>>
>>> It isn't finished yet (documentation, etc) but it should work.
>>>
>>> Jakub
>>>
>>> On Thu, Aug 25, 2022 at 1:18 PM TommyLike Hu  wrote:
>>> >
>>> > Thanks, that's incredible! I will follow your guidance and have a try :)
>>> >
>>> > On Thu, Aug 25, 2022 at 6:40 PM Sérgio Basto  wrote:
>>> >>
>>> >> On Thu, 2022-08-25 at 15:47 +0800, TommyLike Hu wrote:
>>> >>
>>> >> Hey COPR team,
>>> >>Is there any document on how to run a COPR server on the kubernetes 
>>> >> cluster? Including the builder if it's possible.
>>> >>
>>> >>
>>> >> You have http://frostyx.cz/posts/copr-docker-compose-without-supervisord 
>>> >> and previous article https://frostyx.cz/posts/copr-stack-dockerized
>>> >>
>>> >> here is my notes when I build my copr builder (based on previous article 
>>> >> mention here):
>>> >>
>>> >> dnf install docker docker-compose podman
>>> >> /usr/sbin/usermod -a -G docker sergiomb
>>> >> cat /etc/group | grep sergiomb
>>> >> systemctl start docker
>>> >>
>>> >> user:
>>> >> git clone https://pagure.io/copr/copr.git
>>> >> cd copr/
>>> >> docker-compose up -d
>>> >>
>>> >>
>>> >> after we need init database and add create the chroots
>>> >> docker exec -it copr_frontend_1 bash
>>> >> cat /usr/bin/init-database.sh
>>> >> #!/bin/bash
>>> >>
>>> >> cd /usr/share/copr/coprs_frontend/ && copr-frontend create-db --alembic 
>>> >> alembic.ini
>>> >> copr-frontend create-chroot
>>> >> $(ls /etc/mock/{fedora--{i386,x86_64}.cfg,epel--x86_64.cfg} |xargs -I{} 
>>> >> -n1 basename {} .cfg)
>>> >>
>>> >> and the problems start here
>>> >> the components of corp use corp rpms on 
>>> >> https://copr.fedorainfracloud.org/coprs/g/copr/copr/ and not the git 
>>> >> source , so the fix on git aren't there
>>> >>
>>> >> @copr/copr Copr
>>> >> we need this commit 
>>> >> https://pagure.io/copr/copr/c/0e1e9b20ad5d2a72e6368e353078cca0bea75dab?branch=main
>>> >>  to init db
>>> >>
>>> >> Commit - copr/copr - 0e1e9b20ad5d2a72e6368e353078cca0bea75dab - Pagure.io
>>> >> copr / copr Clone Source Code GIT Documentation GIT Learn more about 
>>> >> these different git repos.
>>> >> and we need this commit 
>>> >> https://pagure.io/copr/copr/c/15726fc653461d8e0309602b70c4ad23984c0fff?branch=main
>>> >>  to builder sign the packages (this one is docker configuration should 
>>> >> be transparent)
>>> >>
>>> >> Commit - copr/copr - 15726fc653461d8e0309602b70c4ad23984c0fff - Pagure.io
>>> >> copr / copr Clone Source Code GIT Documentation GIT Learn more about 
>>> >> these different git repos.
>>> >> copr-frontend create-chroot also have issues that I solved manua

Re: Suggestion: Make it obvious where the build logs?

[Jakub Kadlcik]

Hello Barry,
thank you for the feedback.

> Maybe make "See logs for more details." link logs to the chroot?

That could work when the build is submitted to only one chroot. But
usually, a build is submitted into many chroots, and if more of them
fail, what would we link then?

The results table, where chroot names are, contains also a Logs column
with links to logs for each of the chroots. So maybe just rewording
the "Build failed. See logs for more details." to say something like
"Build failed. For more information see logs in the results section"?

Jakub

On Fri, Aug 26, 2022 at 5:26 PM Barry Scott  wrote:
>
> I'm looking at this page:
>
> https://copr.fedorainfracloud.org/coprs/barryascott/python-qt6/build/4769202/
>
> Status: failed - Build failed. See logs for more details.
>
> I do not see an obvious link to the "logs" that it is telling to me view.
>
> After enough clicking I figured out that its in the chroot that I need to 
> look.
>
> Maybe make "See logs for more details." link logs to the chroot?
>
> Barry
> ___
> copr-devel mailing list -- copr-devel@lists.fedorahosted.org
> To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
> Do not reply to spam, report it: 
> https://pagure.io/fedora-infrastructure/new_issue
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Running COPR on kubernetes cluster?

[Jakub Kadlcik]

Hello,
I hope you found the blog post helpful.

There is also an open pull request allowing to run Copr in OpenShift
https://pagure.io/copr/copr/pull-request/2193

It isn't finished yet (documentation, etc) but it should work.

Jakub

On Thu, Aug 25, 2022 at 1:18 PM TommyLike Hu  wrote:
>
> Thanks, that's incredible! I will follow your guidance and have a try :)
>
> On Thu, Aug 25, 2022 at 6:40 PM Sérgio Basto  wrote:
>>
>> On Thu, 2022-08-25 at 15:47 +0800, TommyLike Hu wrote:
>>
>> Hey COPR team,
>>Is there any document on how to run a COPR server on the kubernetes 
>> cluster? Including the builder if it's possible.
>>
>>
>> You have http://frostyx.cz/posts/copr-docker-compose-without-supervisord and 
>> previous article https://frostyx.cz/posts/copr-stack-dockerized
>>
>> here is my notes when I build my copr builder (based on previous article 
>> mention here):
>>
>> dnf install docker docker-compose podman
>> /usr/sbin/usermod -a -G docker sergiomb
>> cat /etc/group | grep sergiomb
>> systemctl start docker
>>
>> user:
>> git clone https://pagure.io/copr/copr.git
>> cd copr/
>> docker-compose up -d
>>
>>
>> after we need init database and add create the chroots
>> docker exec -it copr_frontend_1 bash
>> cat /usr/bin/init-database.sh
>> #!/bin/bash
>>
>> cd /usr/share/copr/coprs_frontend/ && copr-frontend create-db --alembic 
>> alembic.ini
>> copr-frontend create-chroot
>> $(ls /etc/mock/{fedora--{i386,x86_64}.cfg,epel--x86_64.cfg} |xargs -I{} -n1 
>> basename {} .cfg)
>>
>> and the problems start here
>> the components of corp use corp rpms on 
>> https://copr.fedorainfracloud.org/coprs/g/copr/copr/ and not the git source 
>> , so the fix on git aren't there
>>
>> @copr/copr Copr
>> we need this commit 
>> https://pagure.io/copr/copr/c/0e1e9b20ad5d2a72e6368e353078cca0bea75dab?branch=main
>>  to init db
>>
>> Commit - copr/copr - 0e1e9b20ad5d2a72e6368e353078cca0bea75dab - Pagure.io
>> copr / copr Clone Source Code GIT Documentation GIT Learn more about these 
>> different git repos.
>> and we need this commit 
>> https://pagure.io/copr/copr/c/15726fc653461d8e0309602b70c4ad23984c0fff?branch=main
>>  to builder sign the packages (this one is docker configuration should be 
>> transparent)
>>
>> Commit - copr/copr - 15726fc653461d8e0309602b70c4ad23984c0fff - Pagure.io
>> copr / copr Clone Source Code GIT Documentation GIT Learn more about these 
>> different git repos.
>> copr-frontend create-chroot also have issues that I solved manually directly 
>> on database , after talk with copr guys , and is running smooth
>>
>> ___
>> copr-devel mailing list -- copr-devel@lists.fedorahosted.org
>> To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
>> Fedora Code of Conduct: 
>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives: 
>> https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
>> Do not reply to spam, report it: 
>> https://pagure.io/fedora-infrastructure/new_issue
>>
>>
>> --
>>
>> Sérgio M. B.
>>
>> ___
>> copr-devel mailing list -- copr-devel@lists.fedorahosted.org
>> To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
>> Fedora Code of Conduct: 
>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives: 
>> https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
>> Do not reply to spam, report it: 
>> https://pagure.io/fedora-infrastructure/new_issue
>
> ___
> copr-devel mailing list -- copr-devel@lists.fedorahosted.org
> To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
> Do not reply to spam, report it: 
> https://pagure.io/fedora-infrastructure/new_issue
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Configuring tito's CoprReleaser to upload to copr.fedorainfracloud.org

[Jakub Kadlcik]

Hello Matt,

> Can anyone point to an example of configuring tito's CoprReleaser

For example the Tito project itself
https://github.com/rpm-software-management/tito/blob/master/.tito/releasers.conf#L15

> but that's a problem because the rpm build [1] requires internet access.

There is an option "Enable internet access during builds" for this in
a project settings but I can see you have this already enabled. Are
you encountering any network-related issues from your CoprReleaser
builds?

Jakub

On Wed, Aug 3, 2022 at 9:34 AM Matt Hickford  wrote:
>
> Hi. Can anyone point to an example of configuring tito's CoprReleaser [2] to 
> upload SRPM to copr.fedorainfracloud.org ? Currently my copr package [1] 
> builds from a GitHub repo but that's a problem because the rpm build [1] 
> requires internet access.
>
> Thanks for reading
> -Matt
>
> [0] my copr package 
> https://copr.fedorainfracloud.org/coprs/matthickford/git-credential-manager/
> [1] my rpm spec 
> https://github.com/hickford/git-credential-manager/blob/rpm/git-credential-manager.spec
> [2] 
> https://github.com/rpm-software-management/tito/blob/master/releasers.conf.5.asciidoc#releasers
> [3] https://docs.pagure.org/copr.copr/user_documentation.html#tito
>
>
> ___
> copr-devel mailing list -- copr-devel@lists.fedorahosted.org
> To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
> Do not reply to spam, report it: 
> https://pagure.io/fedora-infrastructure/new_issue
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: COPR modular odds

[Jakub Kadlcik]

Hello Cristian,
my apologies for the late reply.

All the questions you ask are valid and understandable. The worst
thing is, that I don't have many positive answers for you.

The modularity support for Copr was implemented in the very early
stage of the Fedora Modularity project itself. IIRC back then it
wasn't known how modules will be updated. Or perhaps it was but we
postponed this with one big TODO. The modularity features in Copr were
revamped and completely rewritten several times since then but the
module updates were never finished, and I am very sorry about that.


> $ copr build-module test --yaml dummy.yaml
> "Module dummy-master-20220701234448 already exists"
> Q: Then how can add *newer* package builds to an existing module ?

Please correct me, but to my understanding, a module is identified as a
name-stream-version. The name-stream part is manually defined but the
version is automatically generated

https://github.com/fedora-modularity/libmodulemd/blob/main/yaml_specs/modulemd_stream_v2.yaml#L64=

Therefore, I think two modules shouldn't have the same NSV.

AFAIK we are not supposed to have the "version: ..." defined in the
YAML file, for it to be automatically generated. Then updating a
package in a module should work as simply resubmitting the module
again - it will have the same name-stream but a newer version.

(If anyone can confirm that this is how it is supposed to work, please do so)


> Q: How can one delete an existing module from COPR (assume it was created 
> erroneously
> or obsoleted) ?

Deleting modules was not implemented yet :-/


> Q: How can I avoid having (too) many separate *.repo for each separate module 
> within a
> single project ?
> Q: Is there a unified way to add only once a *.repo (easy to advertise URL) 
> and see
> all the modules within that project ?

I agree with you here, the way to enable modules is awful. There
should be a single modularity repository per project or repository for
each name-stream. And easy `dnf copr` command to enable
it. Unfortunately, it wasn't implemented yet :-/


> Q: Modular builds in the web-frontend expose +extra "Module:" tag, how can 
> copr-cli
> launch builds into such a module-tag ?

I am not sure what "Module:" tag you mean.


> My interest is the ability to have mixed stable/nightly releases (user 
> switchable), so
> the modularity feature would be ideal.

I agree that this would be a good use-case for modularity but I am not
sure that the modularity implementation in Copr is smooth enough for
this. It's up to you. If I could propose a workaround solution, many
other people/teams do this by having two separate projects. One for
nightly builds, one for stable packages. For example

https://copr.fedorainfracloud.org/coprs/g/mock/mock/
https://copr.fedorainfracloud.org/coprs/g/mock/mock-stable/


Jakub

On Sat, Jul 2, 2022 at 11:14 AM Cristian Balint
 wrote:
>
>
> Dear COPR Team,
>
> Would like to ask a few questions after hitting odds trying to use the 
> modular features.
> My interest is the ability to have mixed stable/nightly releases (user 
> switchable), so the modularity feature would be ideal.
>
> After looking at several related online resources including copr-framework 
> source code I decided to ask right here:
>
> #1. Using specific modulemd.yaml, the new module +creates , +builds, +tags 
> all components picked via repo/ref git path.
>
>$ copr build-module test --yaml dummy.yaml
>
>- But running once again (trying to add updated package) with updated 
> ref/tags leads to errors:
>
>$ copr build-module test --yaml dummy.yaml
>"Module dummy-master-20220701234448 already exists"
>
>Q: Then how can add *newer* package builds to an existing module ?
>
>Q: Modular builds in the web-frontend expose +extra "Module:" tag, how can 
> copr-cli launch builds into such a module-tag ?
>
> #2.  Let's assume at #1 modules are created *once* as fixed object and it is 
> not possible to add/alter with newer package builds:
>
>   Q: How can one delete an existing module from COPR (assume it was created 
> erroneously or obsoleted) ?
>
>   Q: How can I avoid having (too) many separate *.repo for each separate 
> module within a single project ?
>
>   Q: Is there a unified way to add only once a *.repo (easy to advertise URL) 
> and see all the modules within that project ?
>
>
> Thank you,
> ~Cristian.
> ___
> copr-devel mailing list -- copr-devel@lists.fedorahosted.org
> To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
> Do not reply to spam on the list, report it: 
> https://pagure.io/fedora-infrastructure
___
copr-devel mailing list --

Re: Outage: Upgrade of Copr servers - 2022-02-03 11:00 UTC

[Jakub Kadlcik]

Hello,
the outage is over and everything should work as expected now.
Sorry for the inconvenience, caused by the downtime.

Jakub

On Wed, Feb 2, 2022 at 11:15 AM Silvie Chlupova  wrote:
>
> There will be an outage starting at:
>
> $ date --date '2022-02-03 11:00 UTC'
>
> The outage will last approximately 2 hours. The copr-backend storage (copr
> build results) will stay online during this outage.
>
> Reason for outage:
> We're updating copr packages to the new versions which will bring new
> features and bugfixes.
>
> Affected Services:
> copr-frontend - https://copr.fedorainfracloud.org
> copr-backend - https://copr-be.cloud.fedoraproject.org/
>
> Contact persons:
> @frostyx / @schlupov
>
> In case of any questions, please join #fedora-buildsys channel on libera.chat 
> or add comment to the  ticket 
> https://pagure.io/fedora-infrastructure/issue/10520
> ___
> copr-devel mailing list -- copr-devel@lists.fedorahosted.org
> To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
> Do not reply to spam on the list, report it: 
> https://pagure.io/fedora-infrastructure
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Move to libra.chat

[Jakub Kadlcik]

To avoid any confusion, there is a typo in the new network name.
It's Libera.chat


Jakub

On Mon, May 31, 2021 at 3:01 PM Miroslav Suchý  wrote:
>
> Hi.
>
> I want to announce that Copr developers have moved from Freenode to 
> Libra.chat. Still #fedora-buildsys there.
>
> For more details see:
>
> https://fedoramagazine.org/irc-announcement-fedora-moving-to-libera-chat/
>
> Miroslav
> ___
> copr-devel mailing list -- copr-devel@lists.fedorahosted.org
> To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
> Do not reply to spam on the list, report it: 
> https://pagure.io/fedora-infrastructure
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Outage: Upgrade of Copr servers - 2021-04-28 11:00 UTC

[Jakub Kadlcik]

There will be an outage starting at:

$ date --date '2021-04-28 11:00 UTC'

The outage will last approximately 3 hours. The copr-backend storage (copr
build results) will stay online during this outage.

Reason for outage:
We're updating copr packages to the new versions which will bring new
features and bugfixes.

Affected Services:
copr-frontend - https://copr.fedorainfracloud.org
copr-backend - https://copr-be.cloud.fedoraproject.org/

Contact persons:
@frostyx / @schlupov

Please join #fedora-admin in irc.freenode.net or add comments to the ticket for
this outage above.

Infra ticket:
https://pagure.io/fedora-infrastructure/issue/9898


Jakub
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Best practices for mass rebuilds in Copr

[Jakub Kadlcik]

Thank you Miro and Inaki,

I created a PR for this change
https://pagure.io/copr/copr/pull-request/1710

Jakub

On Wed, Mar 3, 2021 at 8:51 PM Iñaki Ucar  wrote:
>
> On Wed, 3 Mar 2021 at 20:33, Miro Hrončok  wrote:
> >
> > On 03. 03. 21 20:18, Jakub Kadlčík wrote:
> > > Hello,
> > >
> > > we observe more and more people using Copr for rebuilding large amounts
> > > of packages from some third-party repositories. We have projects
> > > providing all python packages, R packages, we have projects providing
> > > all Fedora packages rebuilt with some proposal change, etc.
> > >
> > > These are all valid use-cases and Copr should be able to sustain such
> > > loads (even though we still have some bottlenecks to get rid of).
> > >
> > > To make the mass-rebuilding experience better for new users, we put
> > > together a short list of best practices.
> > >
> > > https://docs.pagure.org/copr.copr/user_documentation.html#mass-rebuilds
> > >
> > > If you think that some useful tip is missing, let us know.
>
> Very reasonable guidelines, thanks for putting them together.
>
> > I'd add: If possible, use the --background flag when building large amount 
> > of
> > packages.
>
> I was about to add the same. One issue is that some of these mass
> rebuilds are triggered via webhooks, which do not provide the means
> for setting this flag. Reported in [1].
>
> [1] https://pagure.io/copr/copr/issue/1699
>
> Iñaki
>
> >
> > --
> > Miro Hrončok
> > --
> > Phone: +420777974800
> > IRC: mhroncok
> > ___
> > copr-devel mailing list -- copr-devel@lists.fedorahosted.org
> > To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
> > Fedora Code of Conduct: 
> > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives: 
> > https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
> > Do not reply to spam on the list, report it: 
> > https://pagure.io/fedora-infrastructure
>
>
>
> --
> Iñaki Úcar
>
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Unplanned outage 2020-12-29 -- copr keygen timeout

[Jakub Kadlcik]

Hello,
due to not yet known issue, copr-keygen machine stopped responding and
we had to reboot it. As a consequence, we experienced a ~4 hours
outage window during which every submitted build failed.

The unplanned outage:

- started: 2020-12-29 07:22 UTC
- was reported: 2020-12-29 09:48 UTC
- ended: 2020-12-29 11:14 UTC

And builds between 1850184 and 1850351 were affected. Please consider
resubmitting them. Everything is up and running now.


Sorry for the inconvenience,
Jakub
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org

Re: Please raise build time limit for Chromium again

[Jakub Kadlcik]

Thank you for keeping us posted. It is interesting to know how long
the biggest packages take.


Jakub

On Sun, Dec 13, 2020 at 5:20 PM 藍挺瑋  wrote:
>
> Jakub Kadlcik 於 2020/12/6 下午8:57 寫道:
> > Hello,
> > I increased the max build time limit to 48h as you requested.
>
> Thank you. I got a successful build of Chromium 87.0.4280.88 several
> days ago [1]. It took about 31 hours.
>
> > Just for reference if someone else is reading this, it is not a
> > default build time, that remains 5h. But it is possible to specify a
> > higher value, please see
> > https://docs.pagure.org/copr.copr/release-notes/2020-11-13.html#per-build-timeout-implemented
> >
> >
> > Jakub
>
> [1] https://copr.fedorainfracloud.org/coprs/lantw44/chromium/build/1816762/
>
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org

Re: Please raise build time limit for Chromium again

[Jakub Kadlcik]

Hello,
I increased the max build time limit to 48h as you requested.

Just for reference if someone else is reading this, it is not a
default build time, that remains 5h. But it is possible to specify a
higher value, please see
https://docs.pagure.org/copr.copr/release-notes/2020-11-13.html#per-build-timeout-implemented


Jakub

On Sun, Dec 6, 2020 at 11:47 AM 藍挺瑋  wrote:
>
> Since ld.gold segfault on Fedora 33 and rawhide when it uses more than
> one thread [1], I switched my Chromium builds to use ld.bfd a few months
> ago. The change increased the build time, but at least the build didn't
> fail in 1 hour due to ld.gold segfault.
>
> It seems that Chromium 87 increases the build time further with its
> Ozone platform. Now it is very hard to get successful builds of Chromium
> 87 on Copr. After submitting Chromium 87.0.4280.66 builds for more than
> 10 times, I still couldn't get successful builds for all chroots. Even
> if there were successful builds in some chroots, the build time was
> pretty close to the limit. For example, this build [2] took 29h 50m for
> Fedora 33, and this build [3] took 29h 52m for Fedora rawhide.
>
> Is it possible to raise the limit again? Given that Chromium keeps
> increasing the build time for the past 2 years, I think we should raise
> the limit to 48 hours this time.
>
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1873848
> [2] https://copr.fedorainfracloud.org/coprs/lantw44/chromium/build/1782394/
> [3] https://copr.fedorainfracloud.org/coprs/lantw44/chromium/build/1794997/
> ___
> copr-devel mailing list -- copr-devel@lists.fedorahosted.org
> To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org

Re: Disabling Fedora 30 chroots in Copr

[Jakub Kadlcik]

Hello Alexander,
what do those chroots say in their "Remaining time" column, please?


Jakub

On Mon, Nov 23, 2020 at 8:34 AM Alexander Ploumistos
 wrote:
>
> Hello Jakub,
>
> I noticed that some of my projects still have chroots for even older
> releases, e.g. F28, F29 without the option to remove them. In another
> instance, only a specific F30 arch shows up among the chroots to be
> removed or extended, while the others architectures are not picked up.
> Is there something I can do to remove them, other than deleting the
> entire build along with every other chroot?
>
> Best regards,
> A.
> ___
> devel mailing list -- de...@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org

Re: Disabling Fedora 30 chroots in Copr

[Jakub Kadlcik]

Hello again,

the Fedora 30 chroots are disabled for around three months now but so far we
haven't marked the built results as outdated. I did it just now, so
according to Outdated chroots removal policy [1], Copr is
going to preserve existing build results in those chroots for another
180 days and then automatically remove them unless you take an action
and prolong the chroots life span in your projects. Read more about this
feature in the  Copr - Removing outdated chroots blog post [2].

The email notifications for upcoming deletion proved to be unreliable
for some users in the past, therefore we tried to improve this
situation within the latest Copr release [3]. We added some on-page
notifications [4] to let you know if some of your chroots are about to
be deleted soon. We also added a page that shows outdated chroots from
all projects that you are an admin of. This should give you a much
better overview than having to go through all projects and looking
into their settings. It also gives you an option to be proactive, and
add a task to your calendar to prolong the chroots that you care
about, and repeat it once in a few months. It shouldn't take more than
a couple of minutes to complete. Please log-in and see
https://copr.fedorainfracloud.org/user/repositories/


[1] https://docs.pagure.org/copr.copr/copr_outdated_chroots_removal_policy.html
[2] http://frostyx.cz/posts/copr-removing-outdated-chroots
[3] https://docs.pagure.org/copr.copr/release-notes/2020-11-13.html
[4] 
https://docs.pagure.org/copr.copr/release-notes/2020-11-13.html#eol-chroot-repositories

Jakub

On Tue, Aug 18, 2020 at 3:12 PM Jakub Kadlcik  wrote:
>
> Hello,
>
> we have just disabled Fedora 30 chroots in Copr.
>
> According to the Fedora wiki [1], Fedora 30 reached the end of its life
> on 2020-05-26 and therefore we are disabling it in Copr.
>
> That effectively means that from this moment, it is no longer possible
> to submit builds for the following chroots:
>
> - fedora-30-x86_64
> - fedora-30-i386
> - fedora-30-ppc64le
> - fedora-30-aarch64
> - fedora-30-armhfp
>
> [1] https://fedoraproject.org/wiki/End_of_life
>
>
> Jakub
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org

Builders upgraded to F33

[Jakub Kadlcik]

Hello,
we have upgraded the builder images to Fedora 33. Please note, that it
will take some time until all builders get recycled and relaunched
from the new images.


COPR team,
Jakub
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org

Re: faccessat2 support in COPR

[Jakub Kadlcik]

Hello Florian,
I must confess that this is a too system-level topic for me to
comprehend, but I read the BZ 1869030 you linked and I think your
question boils down to this?

> In summary:
> - We need to check with COPR admins to see if their systemd-nspawn is new 
> enough to drop the patch.

At this moment, Copr builders are F32 instances spawned from our
snapshot, that was created Sep 18 2020, and therefore contain package
versions from that date. We have systemd-container installed in
245.7-1 version but on that system 245.8-2 is available. We can update
the snapshot for you, if necessary. In case even newer version is
required, please let me know where to get it.

I hope I am not misunderstanding the question completely.


Jakub


On Tue, Oct 20, 2020 at 4:02 PM Florian Weimer  wrote:
>
> Do the COPR environments either support faccessat2 or fail with ENOSYS?
>
> I've been told that we put in a workaround in glibc for the bogus EPERM
> error from systemd-nspawn specifically to support COPR:
>
>   
>
> And we really need to remove that workaround again because EPERM is an
> ambiguous error code and applies to situations where we *do not* want to
> perform the fallback implementation (because it cannot perform
> permission checks accurately).
>
> Thanks,
> Florian
> --
> Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn,
> Commercial register: Amtsgericht Muenchen, HRB 153243,
> Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael 
> O'Neill
> ___
> copr-devel mailing list -- copr-devel@lists.fedorahosted.org
> To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org

Builders upgraded to F32

[Jakub Kadlcik]

Hello,
we have upgraded the builder image to Fedora 32. Please note, that it
will take some time until all builders get recycled and relaunched
from the new image.


COPR team,
Jakub
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org

Re: Seeking ppc64le support in Fedora copr

[Jakub Kadlcik]

Hello Gris,

at the beginning of 2020, there was a big migration of Fedora
infrastructure from a datacenter
in Arizona to a new one in Virginia.

https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org/thread/PN6RL7XT3V7DVC7MK46H3QDEJPL5FRI6/

This move affected also Copr servers and builders, which we have
temporarily moved to Amazon AWS,
so they could continue running without any downtime.

Unfortunately, it doesn't provide support for running ppc64le
instances and therefore we are waiting for our previous hardware to be
re-assembled and ready for us. At this moment I don't have any ETA but
I will try to find out and let you know.

There is a related thread, you might find useful.

https://lists.fedoraproject.org/archives/list/copr-devel@lists.fedorahosted.org/thread/CCQRCHTOU2WQ5JAVLRI6MOS6IBIDU2XN/


Jakub

On Wed, Sep 9, 2020 at 2:24 PM Gris Ge  wrote:
>
> Hi Team,
>
> The copr was used to have epel-8-ppc64le support[1], but now it is gone
> from webpage, any idea why and how to enable it again?
>
> Thank you!
> Best regards.
>
> [1]: 
> https://copr.fedorainfracloud.org/coprs/nmstate/nmstate-0.2/build/1237626/
> --
> Gris Ge
> ___
> copr-devel mailing list -- copr-devel@lists.fedorahosted.org
> To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org

Re: Highlights from the latest Copr release

[Jakub Kadlcik]

>  Project karma implemented; Logged-in users can give
>  thumbs-up/thumbs-down to the existing copr projects.  This is just
>  another way to give feedback about a particular Copr project quality.
>  This is merely subjective.  We do not give you guidance what "thumbs
>  up/down" means.  When it is good for you - for whatever reason - give it
>  thumbs up.  It may be just feedback for the maintainer or other users.
>  Or we may automatically select and group high-quality projects in the
>  future - and e.g. revive the idea of the Playground [1].  The options
>  are open. We would like to hear your feedback about this feature!

For anyone interested, I wrote a blog post about this feature
http://frostyx.cz/posts/upvoting-projects-in-copr


Jakub

On Wed, Aug 12, 2020 at 3:38 PM Pavel Raiskup  wrote:
>
> On Wednesday, August 12, 2020 2:29:25 PM CEST Vít Ondruch wrote:
> > Dne 12. 08. 20 v 10:29 Pavel Raiskup napsal(a):
> > > - Copr newly provides a build-time macro %buildtag.  Its format is
> > >   `.copr` and is useable for auto-incrementing the package's NVR
> > >   in subsequent builds.  It may be used in spec file like:
> > >
> > > Release: 1%{?dist}%{?buildtag}
> >
> > Not bad, but I think we don't want to promote new (and more over Copr
> > specific) macro in Fedora. IHO, it would be much better if Copr modified
> > the %{dist} macro appending the %{buildtag}.
>
> It's good idea, but not as trivial as the additional tag.  You need knobs
> turning this on/off, etc.  Patches towards this are welcome I think, but
> it will not be cheap (and it will collide with e.g. %forgemeta and
> others).
>
> This isn't really a promoting of something, but mostly R&D && RFC.  As a
> potential _compromise_ solving the auto-bumping problem cheaply.  Yeah, on
> one-hand it is awesome to see how much energy our community has to to
> solve the problem, but OTOH it really hurts, ... that many man-hours on
> such trivial thing ...
>
> > lso, %{buildtag} is such generic name which on one hand does not say
> > anything about its purposed
>
> Do you have ideas how to change this?
>
> > while there is chance it might collide with something.
>
> Yes.  Unlikely, but yes.  Ideas how to prevent this?
>
> > So why you have not chosen %{buildid} or even %{coprbuildid}.
>
> Because we didn't want to create copr-only solution.  It's R&D, but if
> successful, we can just use the tag as is elsewhere..
>
> Pavel
>
>
> ___
> copr-devel mailing list -- copr-devel@lists.fedorahosted.org
> To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org

Disabling Fedora 30 chroots in Copr

[Jakub Kadlcik]

Hello,

we have just disabled Fedora 30 chroots in Copr.

According to the Fedora wiki [1], Fedora 30 reached the end of its life
on 2020-05-26 and therefore we are disabling it in Copr.

That effectively means that from this moment, it is no longer possible
to submit builds for the following chroots:

- fedora-30-x86_64
- fedora-30-i386
- fedora-30-ppc64le
- fedora-30-aarch64
- fedora-30-armhfp

[1] https://fedoraproject.org/wiki/End_of_life


Jakub
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org

Re: Outage: Upgrade of Copr servers - 2020-08-12 7:00 UTC (Wednesday)

[Jakub Kadlcik]

The outage is now over,
thank you for your patience.

You can see release notes here
https://lists.fedoraproject.org/archives/list/copr-devel@lists.fedorahosted.org/thread/S7EXSR4UX4KQO32PYDBNQHVPAWFFVGWK/


Jakub

On Mon, Aug 10, 2020 at 7:20 PM Jakub Kadlcik  wrote:
>
> There will be an outage starting at:
>
> $ date --date '2020-08-12 7:00 UTC'
>
> The outage will last approximately 3 hours. The copr-backend storage (copr
> build results) will stay online during this outage.
>
> Reason for outage:
> We're updating copr packages to the new versions which will bring new
> features, bugfixes but especially better performance.
>
> Affected Services:
> copr-frontend - https://copr.fedorainfracloud.org
> copr-backend - https://copr-be.cloud.fedoraproject.org/
>
> Contact persons:
> @praiskup/@frostyx
>
> Please join #fedora-admin in irc.freenode.net or add comments to the ticket 
> for
> this outage above.
>
> Ticket Link:
> https://pagure.io/fedora-infrastructure/issue/9218
>
>
> Jakub
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org

Outage: Upgrade of Copr servers - 2020-08-12 7:00 UTC (Wednesday)

[Jakub Kadlcik]

There will be an outage starting at:

$ date --date '2020-08-12 7:00 UTC'

The outage will last approximately 3 hours. The copr-backend storage (copr
build results) will stay online during this outage.

Reason for outage:
We're updating copr packages to the new versions which will bring new
features, bugfixes but especially better performance.

Affected Services:
copr-frontend - https://copr.fedorainfracloud.org
copr-backend - https://copr-be.cloud.fedoraproject.org/

Contact persons:
@praiskup/@frostyx

Please join #fedora-admin in irc.freenode.net or add comments to the ticket for
this outage above.

Ticket Link:
https://pagure.io/fedora-infrastructure/issue/9218


Jakub
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org

Re: Legal flag raised on cran

[Jakub Kadlcik]

On Saturday, there was also stuck copr-dist-git process so for some
time basically nothing was happening.
Once I restarted the distgit service we were immediately back to ~60
builds running.

That was from around 10:00 UTC (reported on IRC, but it probably
happened minutes or hours earlier)
and was fixed at 10:30 UTC. This _downtime_ was completely unrelated
to iucar/cran project.


Jakub

On Sun, May 31, 2020 at 4:35 PM Iñaki Ucar  wrote:
>
> On Sun, 31 May 2020 at 15:14, Pavel Raiskup  wrote:
> >
> > On Sunday, May 31, 2020 7:20:20 AM CEST you wrote:
> > > This COPR just creates too much tasks for building and other waiting 
> > > longer
> > > for available builders.
> > >
> > > Navigate to https://copr.fedorainfracloud.org/admin/legal-flag/
> > > Contact on owner is: iucar 
> >
> > We are aware that the build scheduling is not fair (next release will
> > solve this once and forever, patches are already merged), but even now
> > builds in one project can not delay builds in other projects..  We have
> > 50 x86_64 builder machines, and one project can only waste 8 builders at
> > the same time.  Can you elaborate on the problems you had?  There probably
> > was much more request from different projects?
>
> FWIW, it seems that there was some issue downloading the upstream repo
> information in yesterday's daily sync, and due to this, some packages
> that didn't require an update were wrongly indentified as an update.
> As a result, there was a peak of builds, but normally only 40-50
> packages are updated everyday.
>
> --
> Iñaki Úcar
> ___
> copr-devel mailing list -- copr-devel@lists.fedorahosted.org
> To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org

Re: Outage: Migration of Copr servers - 2020-02-23 06:00 UTC

[Jakub Kadlcik]

I would like to happily announce, that the migration was successful
and the outage is finally over. Everything should work as expected.

The outage window in which Copr services were unavailable, took
~7 hours and most of it was spent by waiting until the final data
sync finishes, so the migration couldn't happen any faster than that.

On the positive note, we are finally going to add F32 chroots
since the migration was the only blocker for that.

Also, please know that we needed to temporarily disable ppc64le
chroots (as it was previously announced) because at this moment
we don't have access to any builders on that architecture.


Thank you for understanding,
Jakub

On Thu, Feb 20, 2020 at 10:43 AM Pavel Raiskup  wrote:
>
> Another thing good to warn about WRT the movement:
> https://pagure.io/copr/copr/issue/1278
>
> We can not enable Fedora 32 chroots in Fedora Copr at this moment.  It
> would mean several new hundreds of gigabytes of data for us to rsync to
> AWS, and we don't have time for it.
>
> This though means that any build done in Fedora Rawhide is done against
> F33 chroot, and will be later (probably Monday) copied to F32 chroot (for
> those projects that follow fedora branching).  So the builds are going to
> be copied even though they can be incompatible.
>
> It might be a good idea to not build against fedora-rawhide* chroots for now,
> till the next week.
>
> Thanks for understanding,
> Pavel
>
>
> On Wednesday, February 19, 2020 2:13:53 PM CET Jakub Kadlcik wrote:
> > There will be an outage starting at 2020-02-23 06:00 UTC, which will last
> > approximately 7 hours (but can take more if something goes wrong).
> >
> > To convert UTC to your local time, take a look at
> > https://fedoraproject.org/wiki/UTCHowto
> > or run:
> >
> > date -d '2020-02-23 06:00 UTC'
> >
> > Reason for outage:
> >
> > Moving Copr servers from OpenStack to Amazon AWS because OpenStack is
> > going to be shut down soon.
> >
> > Affected Services:
> >
> > copr-frontend - https://copr.fedorainfracloud.org
> > copr-backend - https://copr-be.cloud.fedoraproject.org/
> > copr-distgit
> > copr-keygen
> >
> > Backend repositories should remain available during the outage.
> >
> > Ticket Link:
> >
> > https://pagure.io/fedora-infrastructure/issue/8668
> >
> > Contact Information:
> >
> > Please join #fedora-admin in irc.freenode.net or add comments to the
> > ticket for this outage above.
> >
> >
> > Jakub
> > ___
> > copr-devel mailing list -- copr-devel@lists.fedorahosted.org
> > To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
> > Fedora Code of Conduct: 
> > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives: 
> > https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
> >
>
>
>
>
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org

Outage: Migration of Copr servers - 2020-02-23 06:00 UTC

[Jakub Kadlcik]

There will be an outage starting at 2020-02-23 06:00 UTC, which will last
approximately 7 hours (but can take more if something goes wrong).

To convert UTC to your local time, take a look at
https://fedoraproject.org/wiki/UTCHowto
or run:

date -d '2020-02-23 06:00 UTC'

Reason for outage:

Moving Copr servers from OpenStack to Amazon AWS because OpenStack is
going to be shut down soon.

Affected Services:

copr-frontend - https://copr.fedorainfracloud.org
copr-backend - https://copr-be.cloud.fedoraproject.org/
copr-distgit
copr-keygen

Backend repositories should remain available during the outage.

Ticket Link:

https://pagure.io/fedora-infrastructure/issue/8668

Contact Information:

Please join #fedora-admin in irc.freenode.net or add comments to the
ticket for this outage above.


Jakub
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org

Re: Disabling Fedora 29 chroots in Copr

[Jakub Kadlcik]

Thank you guys!

Jakub

On Tue, Feb 18, 2020 at 12:42 PM Frantisek Zatloukal
 wrote:
>
> Got one about a day ago :)
>
> On Tue, Feb 18, 2020 at 12:17 PM Jakub Kadlcik  wrote:
>>
>> I would like to ask you, can anyone with non Red Hat email confirm,
>> that they get the notifications? The subject is
>>
>> > [Copr] upcoming deletion of outdated chroots in your projects
>>
>>
>> Thank you,
>> Jakub
>>
>>
>> On Mon, Feb 17, 2020 at 12:21 AM Jakub Kadlcik  wrote:
>> >
>> > Hello,
>> >
>> > we have just disabled Fedora 29 chroots in Copr.
>> >
>> > According to the Fedora wiki [1], Fedora 29 reached the end of its life
>> > on 2019-11-30 and therefore we are disabling it in Copr.
>> >
>> > That effectively means that from this moment, it is no longer possible
>> > to submit builds for the following chroots:
>> >
>> > - fedora-29-x86_64
>> > - fedora-29-i386
>> > - fedora-29-ppc64le
>> > - fedora-29-aarch64
>> >
>> > Additionally, according to Outdated chroots removal policy [2], Copr is
>> > going to preserve existing build results in those chroots for another
>> > 180 days and then automatically remove them unless you take an action
>> > and prolong the chroots life span in your projects. Read more about this
>> > feature in the  Copr - Removing outdated chroots blog post [3].
>> >
>> >
>> > [1] https://fedoraproject.org/wiki/End_of_life
>> > [2] 
>> > https://docs.pagure.org/copr.copr/copr_outdated_chroots_removal_policy.html
>> > [3] http://frostyx.cz/posts/copr-removing-outdated-chroots
>> >
>> > Jakub
>> ___
>> devel mailing list -- de...@lists.fedoraproject.org
>> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>> Fedora Code of Conduct: 
>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives: 
>> https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org
>
>
>
> --
>
> Best regards / S pozdravem,
>
> František Zatloukal
> Quality Engineer
> Red Hat
> ___
> devel mailing list -- de...@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org

Re: Disabling Fedora 29 chroots in Copr

[Jakub Kadlcik]

I would like to ask you, can anyone with non Red Hat email confirm,
that they get the notifications? The subject is

> [Copr] upcoming deletion of outdated chroots in your projects


Thank you,
Jakub


On Mon, Feb 17, 2020 at 12:21 AM Jakub Kadlcik  wrote:
>
> Hello,
>
> we have just disabled Fedora 29 chroots in Copr.
>
> According to the Fedora wiki [1], Fedora 29 reached the end of its life
> on 2019-11-30 and therefore we are disabling it in Copr.
>
> That effectively means that from this moment, it is no longer possible
> to submit builds for the following chroots:
>
> - fedora-29-x86_64
> - fedora-29-i386
> - fedora-29-ppc64le
> - fedora-29-aarch64
>
> Additionally, according to Outdated chroots removal policy [2], Copr is
> going to preserve existing build results in those chroots for another
> 180 days and then automatically remove them unless you take an action
> and prolong the chroots life span in your projects. Read more about this
> feature in the  Copr - Removing outdated chroots blog post [3].
>
>
> [1] https://fedoraproject.org/wiki/End_of_life
> [2] 
> https://docs.pagure.org/copr.copr/copr_outdated_chroots_removal_policy.html
> [3] http://frostyx.cz/posts/copr-removing-outdated-chroots
>
> Jakub
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org

Disabling Fedora 29 chroots in Copr

[Jakub Kadlcik]

Hello,

we have just disabled Fedora 29 chroots in Copr.

According to the Fedora wiki [1], Fedora 29 reached the end of its life
on 2019-11-30 and therefore we are disabling it in Copr.

That effectively means that from this moment, it is no longer possible
to submit builds for the following chroots:

- fedora-29-x86_64
- fedora-29-i386
- fedora-29-ppc64le
- fedora-29-aarch64

Additionally, according to Outdated chroots removal policy [2], Copr is
going to preserve existing build results in those chroots for another
180 days and then automatically remove them unless you take an action
and prolong the chroots life span in your projects. Read more about this
feature in the  Copr - Removing outdated chroots blog post [3].


[1] https://fedoraproject.org/wiki/End_of_life
[2] https://docs.pagure.org/copr.copr/copr_outdated_chroots_removal_policy.html
[3] http://frostyx.cz/posts/copr-removing-outdated-chroots

Jakub
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org

Re: Packages prepared using EL8 chroot are not available for CentOS8

[Jakub Kadlcik]

> The thing is that your project doesn't have the module_hotfixes option
> enabled,

A short blog post on that topic:
http://frostyx.cz/posts/module-hotfixes-in-copr


Jakub

On Mon, Jan 27, 2020 at 2:00 PM Pavel Raiskup  wrote:
>
> On Sunday, January 26, 2020 8:15:11 AM CET Eugene Akhmetkhanov wrote:
> > Hi guys,
> >
> > I have qemu-kvm-4.2.0 packages prepared for CentOS 8 on COPR 
> > https://copr.fedorainfracloud.org/coprs/axmetishe/qemu-kvm/packages/
> > using git repository with spec and I'm trying to install them via 
> > repository but dnf from CentOS 8
> > container can't find them, but src only:
>
> The thing is that your project doesn't have the module_hotfixes option
> enabled, and you are trying to override qemu-kvm which comes from modular
> content.
>
> Modular packages have an unintuitive hack that they beat every other
> concurrent package (of the same name), unless the repo where they come
> from has `module_hotfixes=True`.
>
> This is pretty new feature in Copr (last release, added about a month
> ago).
>
> Pavel
>
> > dnf info qemu-kvm --showduplicates
> > Name : qemu-kvm
> > Epoch: 15
> > Version  : 4.2.0
> > Release  : 68.el8
> > Architecture : src
> > Size : 59 M
> > Source   : None
> > Repository   : copr:copr.fedorainfracloud.org:axmetishe:qemu-kvm
> > Summary  : QEMU is a machine emulator and virtualizer
> > URL  : http://www.qemu.org/
> > License  : GPLv2 and GPLv2+ and CC-BY
> > Description  : qemu-kvm is an open source virtualizer that provides hardware
> >  : emulation for the KVM hypervisor. qemu-kvm acts as a virtual
> >  : machine monitor together with the KVM kernel modules, and 
> > emulates
> >  : the hardware for a full system such as a PC and its 
> > associated
> >  : peripherals.
> >
> > This is wierd because a month ago I was able to bootstrap one instance via 
> > kickstart with this package installation.
> >
> > On the other hand the same command on Fedora 31 show me the packages:
> >
> > dnf info qemu-kvm --showduplicates
> > Name : qemu-kvm
> > Epoch: 15
> > Version  : 4.2.0
> > Release  : 68.el8
> > Architecture : x86_64
> > Size : 7.2 k
> > Source   : qemu-kvm-4.2.0-68.el8.src.rpm
> > Repository   : copr:copr.fedorainfracloud.org:axmetishe:qemu-kvm
> > Summary  : QEMU is a machine emulator and virtualizer
> > URL  : http://www.qemu.org/
> > License  : GPLv2 and GPLv2+ and CC-BY
> > Description  : qemu-kvm is an open source virtualizer that provides hardware
> >  : emulation for the KVM hypervisor. qemu-kvm acts as a virtual
> >  : machine monitor together with the KVM kernel modules, and 
> > emulates
> >  : the hardware for a full system such as a PC and its 
> > associated
> >  : peripherals.
> >
> > Additionally I have the libssh2 package which I'm able to install in this 
> > container.
> >
> > I'm new with COPR and can't get the point why this happens.
> > Would someone point me to the right direction please?
> >
> > Thank you in advance.
> > ___
> > copr-devel mailing list -- copr-devel@lists.fedorahosted.org
> > To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
> > Fedora Code of Conduct: 
> > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives: 
> > https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
> >
>
>
>
> ___
> copr-devel mailing list -- copr-devel@lists.fedorahosted.org
> To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org

Temporarily using `best=False' for EPEL-8 builds in Copr

[Jakub Kadlcik]

Hello,

currently, there is a problem with building EPEL-8 packages because of
DNF bugs regarding modularity (see RHBZ 1758459).

The only known workaround is to use DNF with `best=False'. Even though
it is something you don't really want to use longterm, we are patching
mock configs epel-8-* chroots, so there can be at least some EPEL-8
building in Copr.

(I am doing the change right now, but it won't affect already
spined-up builders. It will take a while until they get recycled and
use new configuration)

Once the DNF issues get resolved, we are going to drop those patches
and use `best=True` again.

For additional information, please see RHBZ 1756681 and RHBZ 1758467.


Thank you for understanding,
Jakub
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org

Backend storage clean-up

[Jakub Kadlcik]

Hello,

we have decided that it is a time to go through Copr backend data and
clean it up a little. Due to several bugs forgetting to remove backend
data after removing their records from the database, _temporarily_
backing up some folder here and there, etc, we ended up with a lot of
unknown data, that should have been already deleted.

So, we wrote a script [1] to find data that should be deleted, and we
... haven't deleted it yet. Instead, we put it aside in a case there
were any false-positives by the script. If you want to be extra safe,
I am attaching a list of all of those files, you may check it.

If you find out, that we accidentally want to remove any of your data
that is still being used, please contact us immediately! Otherwise, we
are going to delete it once we are running out of disk space (which
may not take a lot of time)

[1] 
https://pagure.io/copr/copr/blob/master/f/backend/run/copr_print_results_to_delete.py

Thank you for understanding,
Jakub


results-to-delete.xz
Description: application/xz
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org

Disabling Fedora 28 chroots in Copr

[Jakub Kadlcik]

Hello,

we have just disabled Fedora 28 chroots in Copr.

According to the Fedora wiki [1], Fedora 28 reached the end of its life
on 2019-05-28 and therefore we are disabling it in Copr.

That effectively means that from this moment, it is no longer possible
to submit builds for the following chroots:

- fedora-28-x86_64
- fedora-28-i386
- fedora-28-ppc64le

Additionally, according to Outdated chroots removal policy [2], Copr is
going to preserve existing build results in those chroots for another
180 days and then automatically remove them unless you take an action
and prolong the chroots life span in your projects. Read more about this
feature in the  Copr - Removing outdated chroots blog post [3].


[1] https://fedoraproject.org/wiki/End_of_life
[2] https://docs.pagure.org/copr.copr/copr_outdated_chroots_removal_policy.html
[3] http://frostyx.cz/posts/copr-removing-outdated-chroots

Jakub
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org

Re: Outage: Upgrade of Copr servers - 2019-07-18 05:00 UTC

[Jakub Kadlcik]

The outage is done, all our servers are now running Fedora 30 and
everything should work again.
We apologize for any inconvenience caused by the outage.

Jakub

On Tue, Jul 16, 2019 at 10:03 PM Jakub Kadlcik  wrote:
>
> There will be an outage starting at 2019-07-18 05:00 UTC, which will last
> approximately 6 hours.
>
> To convert UTC to your local time, take a look at
> https://fedoraproject.org/wiki/UTCHowto
> or run:
>
> date -d '2019-07-18 05:00 UTC'
>
> Reason for outage:
>
> Upgrade of Copr servers to Fedora 30.
>
> Affected Services:
>
> copr-frontend - https://copr.fedorainfracloud.org
> copr-backend - https://copr-be.cloud.fedoraproject.org/
> copr-distgit
> copr-keygen
>
> Ticket Link:
>
> https://pagure.io/fedora-infrastructure/issue/8006
>
> Contact Information:
>
> Please join #fedora-admin in irc.freenode.net or add comments to the
> ticket for this outage above.
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org

Outage: Upgrade of Copr servers - 2019-07-18 05:00 UTC

[Jakub Kadlcik]

There will be an outage starting at 2019-07-18 05:00 UTC, which will last
approximately 6 hours.

To convert UTC to your local time, take a look at
https://fedoraproject.org/wiki/UTCHowto
or run:

date -d '2019-07-18 05:00 UTC'

Reason for outage:

Upgrade of Copr servers to Fedora 30.

Affected Services:

copr-frontend - https://copr.fedorainfracloud.org
copr-backend - https://copr-be.cloud.fedoraproject.org/
copr-distgit
copr-keygen

Ticket Link:

https://pagure.io/fedora-infrastructure/issue/8006

Contact Information:

Please join #fedora-admin in irc.freenode.net or add comments to the
ticket for this outage above.
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org

New Copr release

[Jakub Kadlcik]

Hello,
I am happy to announce a new Copr release. This time we have focused mainly
on improving a CI experience and freeing up some disk space, but there is
much more. These are some highlights from this release.


- CLI support for managing permissions
  
  For quite some time, you have asked for a possibility to manage project
  permissions through copr-cli or API. This is now possible, see

  copr-cli request-permissions --help
  copr-cli list-permissions --help
  copr-cli edit-permissions --help


- Temporary projects
  --
  Many people use Copr for CI, which may include creating new projects.
  Those are usually relevant for only a limited time and after that just
  floods up the projects list. Instead of automatizing the deletion of
  old projects all by yourself, try using temporary projects. When creating
  or editing a project, it is possible to set an optional "Delete after days"
  field in the Settings tab. There is also a command line option for this.

  copr-cli create ... --delete-after-days 
  copr-cli modify ... --delete-after-days 


- Automatic removal of old builds
  ---
  Another feature useful for CI, but also for normal projects. Sometimes,
  you don't care about old builds and they just slow working with
  builds table. Avoid this by going to package settings and specifying
  the optional "Max number of builds" parameter. Alternatively, use a
command line.

  copr-cli add-package-* --max-builds 
  copr-cli edit-package-* --max-builds 

This keeps last  builds of this package. Older builds are
automatically deleted.
Note that our general policy for [builds
retention](https://docs.pagure.org/copr.copr/user_documentation.html#how-long-do-you-keep-the-builds)
still applies.


- Pagure CI fixes
  
  Copr is for quite some time listening on fedmsg to react on PR and PUSH
  events from Pagure (both src.fedoraproject.org and pagure.io).
However, previously
  it had several limitations;
  1) only the last commit from "push" or pull-request was analyzed, and thus
  only builds for packages updated by _the last_ commit were triggered, this
  is now fixed and copr analyses complete push/pull-request changes,
  2) only one build per pull-reqeust could ever exist, this artificial rule
  was relaxed and now each PR update (new commit, rebase, ...) triggers
  a new copr build,
  3) the fedmsg listener stopped receiving messages after some time and
  a restart was needed, workaround for this was installed (and we plan to
  move to fedora-messaging which should be more reliable),
  4) there was a small rhbz#1699245 bug.
  As a bonus point, it is now enough to add a pull-request comment with
   `[copr-build]` keyword to manually (re)trigger the CI builds.


- Saving up some disk space
  -
  We are struggling with low disk space and hoping to free some up
  by removing backend and distgit data for old builds. To be specific
- we are now removing:
  * old SRPM import logs
  * old tar files from dist-git look-aside cache
  * SRPM from failed builds older than 14 days


- Turning off notifications for outdated chroots removal
  --
  Talking of disk space, we have recently started sending
  notifications about an upcoming deletion of builds for outdated
  chroots. The notifications suggest that if you still care about
  an outdated distribution, going to project settings and prolong
  the time for which the data is going to be preserved. If you don't
  care about it and don't want to be bothered by emails, you can now
  instantly expire the time and schedule the chroot to be removed.


- Respecting module buildorder
  
  When building a module, the `buildorder` was not respected. This
  issue is now fixed.


- Private data in separate tables
  ---
  We have moved secret/private data about users and projects to
  separate tables. This alone is not very interesting information.
  However, it will allow us to dump our database (except for those
  private tables of course) and share them to the public. This
  will allow you to do custom data analysis and statistics.


Jakub
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org

Outage: Upgrade of Copr servers - 2019-04-24 17:00 UTC

[Jakub Kadlcik]

There will be an outage starting at 2019-04-24 17:00 UTC, which will last
approximately 4 hours.

To convert UTC to your local time, take a look at
https://fedoraproject.org/wiki/UTCHowto
or run:

date -d '2019-04-24 17:00 UTC'

Reason for outage:

Upgrade of Copr services to the newest version.

Affected Services:

copr-frontend - https://copr.fedorainfracloud.org
copr-backend - https://copr-be.cloud.fedoraproject.org/
copr-distgit
copr-keygen

Ticket Link:

https://pagure.io/fedora-infrastructure/issue/7731

Contact Information:

Please join #fedora-admin in irc.freenode.net or add comments to the
ticket for this outage above.
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org

Re: Requesting builder permissions via copr-cli or api

[Jakub Kadlcik]

Hello Jiří,

> I've been investigating whether it's possible to request/apply for
> (builder) permission for a project via copr api or copr-cli.
> I.e. the equivalent of what I can do via
> https://copr.fedorainfracloud.org/coprs///permissions/.
> I haven't seen anything like that in api [1] or "copr-cli modify".

That seems to be a valid request, I've created an RFE for that
https://pagure.io/copr/copr/issue/612

Jakub

On Wed, Mar 27, 2019 at 4:55 PM Jiri Popelka  wrote:
>
> Hello,
>
> I've been investigating whether it's possible to request/apply for
> (builder) permission for a project via copr api or copr-cli.
> I.e. the equivalent of what I can do via
> https://copr.fedorainfracloud.org/coprs///permissions/.
> I haven't seen anything like that in api [1] or "copr-cli modify".
>
> The reason is that with packit [2] we eventually want to have a service
> that would build packages in copr, so that upstream maintainers could
> directly see (in a pull request), whether a upstream change (PR) doesn't
> break in downstream (fedora). And in case they wanted to use their
> existing copr repo, we'd need our service to have builder permission in
> that repo and we don't want to manually request it via web for every
> such project.
>
> Thanks,
> Jiri
>
> [1] https://copr-rest-api.readthedocs.io
> [2] https://github.com/packit-service/packit
> ___
> copr-devel mailing list -- copr-devel@lists.fedorahosted.org
> To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org

Re: Copr is going to remove build data from end-of-life chroots

[Jakub Kadlcik]

The initial batch of emails has been sent, so if you use Copr for some time
and have packages built for F27 and lesser, or EPEL5, you should check
your inbox
for a message with the following subject

[Copr] upcoming deletion of outdated chroots in your projects

It was established, that the data will be preserved for 180 days, but
in the blog post
linked above, it was mentioned, that there is an exception for the
first batch. We need to
free some disk space as soon as possible, therefore this time, the preservation
period is by default only 60 days, however with a possibility to
extend it to 180.
The chroots, that will be outdated in the future will be preserved 180
days by default.

Jakub

On Sun, Mar 10, 2019 at 10:58 PM Jakub Kadlcik  wrote:
>
> Hello,
> I would like to let you know, that in the following few days,
> you will start receiving automatized notifications from Copr,
> telling you about deleting repositories for outdated chroots
> and how to proceed if you want to keep them for your projects.
>
> Please read more information about how it is going to work
> and our motivation for doing so, in my blog post.
> http://frostyx.cz/posts/copr-removing-outdated-chroots
>
> Also, please see the "Outdated chroots removal policy"
> in the Copr documentation.
> https://docs.pagure.org/copr.copr/copr_outdated_chroots_removal_policy.html
>
> Jakub
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org

Fedora 30 chroots now available in Copr

[Jakub Kadlcik]

Hello,
I've just enabled F30 chroots in Copr.

The projects that have "Follow Fedora branching" enabled, have them
automatically activated as well builds from rawhide forked into them.

Jakub
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org

Copr is going to remove build data from end-of-life chroots

[Jakub Kadlcik]

Hello,
I would like to let you know, that in the following few days,
you will start receiving automatized notifications from Copr,
telling you about deleting repositories for outdated chroots
and how to proceed if you want to keep them for your projects.

Please read more information about how it is going to work
and our motivation for doing so, in my blog post.
http://frostyx.cz/posts/copr-removing-outdated-chroots

Also, please see the "Outdated chroots removal policy"
in the Copr documentation.
https://docs.pagure.org/copr.copr/copr_outdated_chroots_removal_policy.html

Jakub
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org

Highlights from the latest Copr release

[Jakub Kadlcik]

Hello,
recently (on Feb 19) a major Copr update took place. It was announced,
but release notes weren't attached. Because a list of all changes
would be long and boring,
I rather decided to present you some highlights of the release.


- Allow per-package chroot-blacklisting by wildcard patterns
  You can configure chroot blacklist in package settings. It is applied when
  building a package from default source in web UI, copr-cli or via
webhook. This feature
  is useful in cases when you have multiple packages per project and
some of them
  are not supposed to build successfully in all enabled chroots. The
configuration
  supports patterns - for example, to not build a package on EPEL, set
chroot blacklist to  `epel-*`.

- Live SRPM build log for custom method
  When building SRPM via custom method, builder log is now live.

- Modularity fixes
  For quite some time it is possible to build modules in Copr, but
last few months it was not
  possible to properly install them with DNF them on user machines due
to changed
  expectations on a repository. This issue is resolved and it is possible to
  install modules as expected.

- Project forks page
  We have added a small number next to the "Fork this project" button.
It indicates
  how many forks the project has. Click on it to see a list of the
forks and their
  owners.

- Build into sub-repository within the project
  When submitting a build in copr-cli, you can now specify the project in the
  following format `owner/project:reponame` which allows you to build into
  a specific sub-repository within the project. It works the same way as the
  automatized builds from pagure pull requests.
  
https://pagure.io/copr/copr/blob/copr-cli-1.78-1/f/cli/man/copr-cli.1.asciidoc#_217

- API function to wait until builds finish [BZ#1258970]
  https://bugzilla.redhat.com/show_bug.cgi?id=1258970
  There is a common use case among users, to submit a build via API
and then wait
  until its finished, to do some business logic. Yet, we didn't provide any way
  to wait on a build and users had to implement it themselves. Now it
is possible
  to use `wait(...)` function for this. For example:

from copr.v3 import Client
client = Client.create_from_config_file()

build1 = client.build_proxy.create_from_file(...)
build2 = client.build_proxy.create_from_scm(...)
finished = wait([build1, build2])
print("Builds have finished {}sucessfully".format(
"" if succeeded(finished) else "un"))

- API errors with correct status codes
  The Legacy API used just two status codes, 200 for success and 500 for error.
  Because the APIv3 is based on it, this flaw remained to its first
release. Now,
  the APIv3 finally returns the correct status codes.

- Speed up several slow frontend pages
  Including the homepage which loaded slowly mainly because of the recent
  builds box on the right side. The select query for this box was improved
  and the time required for its execution halved.

Jakub
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org

New release

[Jakub Kadlcik]

Hello,

we have updated the Copr stack to the newest versions of our packages.
This was a first major release after months, so you can expect many
enhancements.

The common theme for this release was to speed-up the frontend
interface, optimize internals and improve the user experience with
small UI changes.

The full list of release notes might come later.

Regards
COPR team
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org

Outage: Upgrade of Copr servers - 2019-02-14 07:00 UTC

[Jakub Kadlcik]

There will be an outage starting at 2019-02-14 07:00 UTC, which will last
approximately 4 hours.

To convert UTC to your local time, take a look at
https://fedoraproject.org/wiki/UTCHowto
or run:

date -d '2019-02-14 07:00 UTC'

Reason for outage:

Upgrade of Copr services to the newest version.

Affected Services:

copr-frontend - https://copr.fedorainfracloud.org
copr-backend - https://copr-be.cloud.fedoraproject.org/
copr-distgit
copr-keygen

Ticket Link:

https://pagure.io/fedora-infrastructure/issue/7560

Contact Information:

Please join #fedora-admin in irc.freenode.net or add comments to the
ticket for this outage above.
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org

Re: Python client - new build from SPEC file

[Jakub Kadlcik]

Hello Petr,

> I want to create a python script for making the release process more
comfortable (create tag in git repository, updating my spec file and
hopefully upload the file to the COPR).

Just to make sure, that you are not reinventing the wheel by mistake. Do
you know tito [1] and rpkg [2] projects? They do exactly what you are
describing, so if you never heard of them, you should definitely check them
;-)

> My code is as simple as this:

I tried your code and it works for me. Isn't somehow possible, that you
indeed have a wrong API token? The create_from_config_file() function by
default uses the ~/.config/copr file. Please make sure that it exists, has
only one [copr-cli] section and it looks like this

[copr-cli]
login = mysecretlogin
username = frostyx
token = mysecrettoken
copr_url = https://copr.fedorainfracloud.org
# expiration date: 2019-05-04

Please check the expiration date of your token and also that it is equal to
https://copr.fedorainfracloud.org/api/ .

[1] https://github.com/dgoodwin/tito/
[2] https://pagure.io/rpkg-util


Jakub

On Tue, Dec 4, 2018 at 10:08 PM Petr Stefan  wrote:

> Hi,
>
> I'm using COPR for building couple of projects for Fedora and CentOS. Now
> I want to create a python script for making the release process more
> comfortable (create tag in git repository, updating my spec file and
> hopefully upload the file to the COPR). I've found python-copr library and
> it works fine when I want for example to get list of existing builds.
> However, creating a new build fails with CoprRequestException (Login
> invalid/expired. Please visit https://copr.fedorainfracloud.org/api to
> get or renew your API token.). But I guess my token is ok, because it's
> freshly generated and works with other endpoins.
>
> My code is as simple as this:
> --
> from copr.v3 import BuildProxy
> build_proxy = BuildProxy.create_from_config_file()
> result = build_proxy.create_from_file("user", "project",
> "spec/file/path.spec")
> --
>
> Is there any solution to my problem? Thanks,
> /semai
> ___
> copr-devel mailing list -- copr-devel@lists.fedorahosted.org
> To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
>
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org

Builder image upgraded to F28

[Jakub Kadlcik]

Hello,
we have upgraded the builder image to Fedora 28. Please note, that it will
take some time until all builders get recycled and relaunched from the new
image.


COPR team
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/copr-devel@lists.fedorahosted.org/message/5PCT2GNBB4FIVEW27E4HTJ4MOM6R6HUH/

Re: GitHub Apps

[Jakub Kadlcik]

The chart says that we likely want to use GitHub App. It doesn't matter
which way go, you always end up with GitHub App because of "Access
everything? No".

Also, they say this, in the document

> Using OAuth Apps
> - An OAuth App should always act as the authenticated GitHub user,
across all of GitHub
> - Don't build an OAuth App if you want your application to act on a
single repository. With the repo OAuth scope, OAuth apps can act on all of
the authenticated user's repositories.

I have a question about a user-friendliness of these two - GitHub App vs
OAuth App. I am reading through tons of docs, but can't find the answer
anywhere. Do I understand it right, that in case of GitHub App, every user
will need to create his own app to get a new access token and put that into
Copr, but in case of OAuth app, *we* will create an application, put it
somehow into https://github.com/works-with and then a user will just
one-click to allow it and then everything will automagically work?

In such case, OAuth apps may be worth it even though the permission
restriction possibilities are limited (
https://developer.github.com/apps/building-oauth-apps/scopes-for-oauth-apps/
)


Jakub




On Wed, Mar 21, 2018 at 12:57 PM, Pavel Raiskup  wrote:

> On Wednesday, March 21, 2018 12:36:25 PM CET Miroslav Suchý wrote:
> > Dne 21.3.2018 v 12:28 Pavel Raiskup napsal(a):
> > > 4. store **only** the **app** credentials into copr
> >
> > Yes. Only one app for all projects and all githubs and individual
> permission
> > for each specific Github is granted via OAuth.
>
> GitHub OAuth:
>
> pros: users don't have to create custom app (a few clicks anyway)
> cons: that app has complete access to the repo, even push
>
> GitHub App:
>
> pros: users can grant the app to e.g. only set the "CI flags" in PR
> cons: users have to create the custom app in web-ui
>
> To me, we should support both ways (oauth for convenience of users)..  but
> I voted for non-OAuth as that's the only option I would _personaly_
> accept.
>
> Pavel
>
>
> ___
> copr-devel mailing list -- copr-devel@lists.fedorahosted.org
> To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
>
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org

Fedora 28 chroots are available

[Jakub Kadlcik]

Hello,

Fedora 28 chroots were added to Copr. For projects with "Follow Fedora
branching" option enabled, the fedora-28-* chroots were auto-created in
their projects and existing builds from the rawhide chroots were copied
there.

COPR team
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org

Give us a feedback on API situation

[Jakub Kadlcik]

Hello,
we are currently discussing how to deal with the current situation of
inconsistent Copr API.

If you are interested in this topic and want to give us some feedback,
please see the https://pagure.io/copr/copr/issue/218

COPR team
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org

Disabling F25 chroots

[Jakub Kadlcik]

Hello,

since the Fedora 25 reached the end of its life cycle and is now stated as
EOL for more than a month, we've disabled it in Copr.

Don't worry, it just means that it is not possible to submit new builds
against it. The existing builds and repositories are preserved.


COPR team
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org

Re: New release of Copr

[Jakub Kadlcik]

> Looks like it was not implemented in client_v2 in python-copr...

Hi Igor,
the copr-cli still uses the legacy client, so it was added there. We should 
really migrate it to client_v2 and let the old one die.

I don't know what are Mirek's plans for next sprints, but maybe I could work on 
it.

Jakub


- Original Message -
From: "Igor Gnatenko" 
To: "Cool Other Package Repositories" 
Sent: Thursday, June 16, 2016 5:26:24 PM
Subject: Re: New release of Copr

On Thu, Jun 16, 2016 at 3:10 PM, Miroslav Suchy  wrote:
> Hi,
> I just upgraded Copr instance to new version.
>
> There is one big change. You can now lower priority of your build.
> It was introduced to easy rebuild of rubygems and pypi. But it can be used
> by CI systems later.
>
> Copr-cli from our git, has --background option already. It lowers the
> priority. But due compatibility reason we will not push the package into
> main Fedora and we will wait one or two weeks.
Looks like it was not implemented in client_v2 in python-copr...
>
> If you want to give it try, then you can install it from our copr project.
>
> Mirek
> ___
> copr-devel mailing list
> copr-devel@lists.fedorahosted.org
> https://lists.fedorahosted.org/admin/lists/copr-devel@lists.fedorahosted.org



-- 
-Igor Gnatenko
___
copr-devel mailing list
copr-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/admin/lists/copr-devel@lists.fedorahosted.org
___
copr-devel mailing list
copr-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/admin/lists/copr-devel@lists.fedorahosted.org

Copr upgrade

[Jakub Kadlcik]

Hi, today I am proud to announce new Copr release which brings us some very 
interesting new features and a lot of bugfixes.

Highlights:
  - support building from PyPI via pyp2rpm (See some of your projects > 
"Builds" > "New Build" > "PyPI")
  - support project forking [1]
  - dockerized copr-backend for testing purposes [2]


Fixed bugs:
  - 1314920 - No logs when Git or Mock SCM import fails
  - 1314918 - Invalid edit of Package Git/SCM URL in group-owned copr causes 
error 404
  - 1314917 - Cannot unset Git/SCM
  - 1314369 - Exception raised when resubmitting Git&Tito build
  - 1311777 - failure to delete project (and cancelled build)
  - 1307239 - "inline HTMLis forbidden" -> "inline HTML is forbidden"
  - 1306182 - A single failure makes the whole monitoring line red
  - 1304012 - Can't see logs on failed build
  - 1305754 - Incorrect dates are displayed on the build page
  - 1318229 - Can't delete or remove a package definition


[1] http://frostyx.cz/posts/copr-forking-projects
[2] https://fedorahosted.org/copr/wiki/Contribute#Builddockerbackendimage


Jakub
___
copr-devel mailing list
copr-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/admin/lists/copr-devel@lists.fedorahosted.org

Re: Branching of F24

[Jakub Kadlcik]

> ah!, now I understood, the monitor page wasn't updated, the results of
> Fedora 24 builds [1], should also be copied from rawhide, isn't it ?
>
> [1] https://copr.fedorainfracloud.org/coprs/sergiomb/kde4for23/monitor/

Yeah, the backend data such as built .rpm packages are copied and the repodata 
is created so users of F24 should be able to install your packages, which was 
originally built for Fedora Rawhide.

But as you have pointed out, information in monitor and on the build 
information page are missing. Thank you for the feedback, I will enhance this 
and on next branching it will be better :-)

Jakub
___
copr-devel mailing list
copr-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/admin/lists/copr-devel@lists.fedorahosted.org