On Wed, 2022-01-05 at 13:57 +0100, Pavel Raiskup wrote:
> On Wednesday, January 5, 2022 12:42:40 PM CET Sérgio Basto wrote:
> > On Wed, 2022-01-05 at 09:01 +0100, Pavel Raiskup wrote:
> > > On Wednesday, January 5, 2022 1:03:51 AM CET Sérgio Basto wrote:
> > > > On Tue, 2022-01-04 at 22:58 +, S
On Wed, 2022-01-05 at 08:58 +0100, Pavel Raiskup wrote:
> Hi Sérgio,
>
> On Tuesday, January 4, 2022 11:58:32 PM CET Sérgio Basto wrote:
> > now I have the all database of copr production but I want a clean
> > Database and configure my builders ( which is only one x86_64 )
> >
> > I can't get r
On Wednesday, January 5, 2022 12:42:40 PM CET Sérgio Basto wrote:
> On Wed, 2022-01-05 at 09:01 +0100, Pavel Raiskup wrote:
> > On Wednesday, January 5, 2022 1:03:51 AM CET Sérgio Basto wrote:
> > > On Tue, 2022-01-04 at 22:58 +, Sérgio Basto wrote:
> > > > On Tue, 2022-01-04 at 10:35 +0100, Si
On Wed, 2022-01-05 at 09:01 +0100, Pavel Raiskup wrote:
> On Wednesday, January 5, 2022 1:03:51 AM CET Sérgio Basto wrote:
> > On Tue, 2022-01-04 at 22:58 +, Sérgio Basto wrote:
> > > On Tue, 2022-01-04 at 10:35 +0100, Silvie Chlupova wrote:
> > > > Hi Sérgio,
> > > > I can reproduce your probl
On Wed, 2022-01-05 at 09:19 +0100, Silvie Chlupova wrote:
> I don't know what your scenario is that you want to have your own
> Copr, however, disabling package signing could temporarily solve your
> problem. Set do_sign=false in the copr_backend-build_1 container in
> the /etc/copr/copr-be.conf fi
I don't know what your scenario is that you want to have your own Copr,
however, disabling package signing could temporarily solve your problem.
Set do_sign=false in the copr_backend-build_1 container in the
/etc/copr/copr-be.conf file.
Silvie
On 1/5/22 09:01, Pavel Raiskup wrote:
On Wednesd
On Wednesday, January 5, 2022 1:03:51 AM CET Sérgio Basto wrote:
> On Tue, 2022-01-04 at 22:58 +, Sérgio Basto wrote:
> > On Tue, 2022-01-04 at 10:35 +0100, Silvie Chlupova wrote:
> > > Hi Sérgio,
> > > I can reproduce your problem by deleting the database in the
> > > copr_database_1 container
Hi Sérgio,
On Tuesday, January 4, 2022 11:58:32 PM CET Sérgio Basto wrote:
> now I have the all database of copr production but I want a clean
> Database and configure my builders ( which is only one x86_64 )
>
> I can't get rid of SQL: INSERT INTO dist_git_instance (name, clone_url,
> clone_pack
On Tue, 2022-01-04 at 22:58 +, Sérgio Basto wrote:
> On Tue, 2022-01-04 at 10:35 +0100, Silvie Chlupova wrote:
> > Hi Sérgio,
> > I can reproduce your problem by deleting the database in the
> > copr_database_1 container and then running init-database.sh in the
> > frontend container. You are m
On Tue, 2022-01-04 at 10:35 +0100, Silvie Chlupova wrote:
> Hi Sérgio,
> I can reproduce your problem by deleting the database in the
> copr_database_1 container and then running init-database.sh in the
> frontend container. You are missing the relations in copr_database_1.
> You can download the d
Hi Sérgio,
I can reproduce your problem by deleting the database in the
copr_database_1 container and then running init-database.sh in the
frontend container. You are missing the relations in copr_database_1.
You can download the database dump here
https://copr.fedorainfracloud.org/db_dumps/
Hi,
I started to build my own copr , I follow
the http://frostyx.cz/posts/copr-docker-compose-without-supervisord
but can't pass the init-database.sh [1], I'm using
https://pagure.io/copr/copr.git 30 dec 2021 commit (f18faf4f)
any tip ?
[1]
docker exec -it copr_frontend_1 bash
cd /usr/share/
12 matches
Mail list logo
