help with building a package with Copr
by Marc Dequènes (Duck)
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--mQV5JuiKpPFiR9pN9dNB2kGB0rJwbF2M4
Content-Type: multipart/mixed; boundary="6Xg0Sacgb4pElMTAjEXQqvuhswcRUhHpI";
protected-headers="v1"
From: =?UTF-8?B?TWFyYyBEZXF1w6huZXMgKER1Y2sp?= <duck(a)redhat.com>
To: oVirt Infra <infra(a)ovirt.org>
Message-ID: <ec4d599d-3fcd-2115-62a0-917f22ee397a(a)redhat.com>
Subject: help with building a package with Copr
--6Xg0Sacgb4pElMTAjEXQqvuhswcRUhHpI
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Quack,
So my project is here:
https://copr.fedorainfracloud.org/coprs/duck/PostSRSd/build/568647/
In the SCM URL I've got the spec file.
I built this package on a CentOS 7.3 VM successfully and it currently
works well in production.
On Copr I've got this error:
https://copr-be.cloud.fedoraproject.org/results/duck/PostSRSd/epel-7-x86_=
64/00568647-postsrsd/build.log.gz
So I made a small change (second commit) to try to make things simpler
just in case but it does not work better.
So I'm at a loss. Could someone give a hand please?
\_o<
--6Xg0Sacgb4pElMTAjEXQqvuhswcRUhHpI--
--mQV5JuiKpPFiR9pN9dNB2kGB0rJwbF2M4
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEcpcqg+UmRT3yiF+BVen596wcRD8FAllLOCIACgkQVen596wc
RD9txxAAsfiVxWQA+qX0ljpavWa6dFKKfPNPDtVqNvRBox5DDGd57qH7BBwH1OdE
DxG443B9d9teP8d+RHbjWJgV91rxQCjCyEaPDuHikVN26LAgD+wH6LarII1mNlck
jEMxaTYGi6CR4O4wdWv0/ycG6Qmvhl0Ev+6zJ82470QUtF5SZPLum59D7Iy9+ygU
z55kVEHl04vVKbgNDhbgMB6p8TVFwwJb/m07OERB3DycQ+JLqiMvVhZCUOzaJfzg
0hsOjDMZuGjs1UATBT8GZmGESTv/yzTuLEVhwsBEHR9QOxcIg545qWkc2bWIwdan
Z76aafXEn7pW/ZiQ1Y7gJ5oGwlfCJi7TH5d+nX1PpbSiRB9gxQY8IyRy996XISkK
1Dp6aYkGIDcNN1xNkpd/BqEaNBbzD6J6iBGOM1orD4hdv9LrApvTpF4wiNyyD1ka
PTkeO7OVN8+Y/n2cmbKD1gM/JlYayekfdotPAjo539R8+2zw3mP6F5DSgInJeC8K
ldwZr4oGbEpML8vG9hD58Yp2ZFaV9W6w28c0cPfT5vY7w15n4GXdrjAzT6ha8V+I
U0lH91NytRIAUT63Hyva17hYSe2XhdRXnVosIjSFeQ1ScU9902IroGJOJMZqhvX8
nHWaDCl/dm6StBYxy+ZPIlN+1vgrtJZiVUz59Xl98/Ecr4P2K9w=
=HSyN
-----END PGP SIGNATURE-----
--mQV5JuiKpPFiR9pN9dNB2kGB0rJwbF2M4--
7 years, 5 months
Re: [ovirt-users] [ovirt-devel] Lowering the bar for wiki contribution?
by Roy Golan
Adding infra which I forgot to add from the beginning
On 7 January 2017 at 02:44, Jakub Niedermertl <jniederm(a)redhat.com> wrote:
> On Wed, Jan 4, 2017 at 11:41 AM, Roy Golan <rgolan(a)redhat.com> wrote:
> >
> >
> > On 4 January 2017 at 12:17, Maor Lipchuk <mlipchuk(a)redhat.com> wrote:
> >>
> >>
> >>
> >> On Wed, Jan 4, 2017 at 11:38 AM, Daniel Erez <derez(a)redhat.com> wrote:
> >>>
> >>>
> >>>
> >>> On Wed, Jan 4, 2017 at 9:57 AM, Roy Golan <rgolan(a)redhat.com> wrote:
> >>>>
> >>>> I'm getting the feeling I'm not alone in this, authoring and
> publishing
> >>>> a wiki page isn't as used to be for long time.
> >>>>
> >>>> I want to suggest a bit lighter workflow:
> >>>>
> >>>> 1. Everyone can merge their page - (it's a wiki)
> >>>> Same as with (public and open) code, no one has the motivation to
> >>>> publish a badly written
> >>>> wiki page under their name. True, it can have an impact, but not as
> >>>> with broken code
> >>>>
> >>>
> >>> +1.
> >>> Moreover, I think we shouldn't block any merging. Instead, wiki
> >>> maintainers could act afterwards and revert when needed (Wikipedia
> style).
> >>> Another issue is that (sadly) unlike mediawiki, we need to wait for
> wiki
> >>> publish after a change. So I'd suggest to build and publish the wiki at
> >>> least once a day. Any way, I think we should make the workflow much
> more
> >>> intuitive and pleasant like the previous wiki - i.e. much less
> restrictive
> >>> than manipulating a code base.
> >>>
> >>>
> >>>>
> >>>> 2. Use Page-Status marker
> >>>> The author first merges the draft. Its now out there and should be
> >>>> updated as time goes and its
> >>>> status is DRAFT. Maintainers will come later and after review would
> >>>> change the status to
> >>>> PUBLISH. That could be a header in on the page:
> >>>> ---
> >>>> page status: DRAFT/PUBLISH
> >>>> ---
> >>>>
> >>>> Simple I think, and should work.
> >>>>
> >>
> >> +1
> >> The effort of maintaining the wiki today compare to how it used to be
> >> before is much more cumbersome and problematic.
> >> I think we can learn a lot from wikipedia workflow,
> >> It is a much more inviting process where anyone can change the content
> >> easily.
> >> I'm not saying we should let any anonymous user change the wiki but even
> >> if we make it easier in house we can achieve much more informative
> reliable
> >> and updated wiki.
> >>
> >
> >
> >
> > I really think Github Pages is a perfect fit and an alternative to my
> first
> > suggestion. see
> > https://github.com/oVirt/ovirt-site/wiki/Why-aren't-we-using-this%3F
>
> +1
> Github wiki would allow us instant publishing, review after after
> publishing, it works purely in browser (no need for running local ruby
> server) and it's a service that doesn't require any maintenance form
> our side.
>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> Devel mailing list
> >>>> Devel(a)ovirt.org
> >>>> http://lists.ovirt.org/mailman/listinfo/devel
> >>>
> >>>
> >>>
> >>> _______________________________________________
> >>> Users mailing list
> >>> Users(a)ovirt.org
> >>> http://lists.ovirt.org/mailman/listinfo/users
> >>>
> >>
> >
> >
> > _______________________________________________
> > Users mailing list
> > Users(a)ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> >
>
7 years, 5 months
oVirt infra daily report - unstable production jobs - 360
by jenkins@jenkins.phx.ovirt.org
------=_Part_662_216133554.1498086001714
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Good morning!
Attached is the HTML page with the jenkins status report. You can see it also here:
- http://jenkins.ovirt.org/job/system_jenkins-report/360//artifact/exported...
Cheers,
Jenkins
------=_Part_662_216133554.1498086001714
Content-Type: text/html; charset=us-ascii; name=upstream_report.html
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename=upstream_report.html
Content-ID: <upstream_report.html>
<!DOCTYPE html><head><style type="text/css">
table.gridtable {
border-collapse: collapse;
table-layout:fixed;
width:1600px;
font-family: monospace;
font-size:13px;
}
.head {
font-size:20px;
font-family: arial;
}
.sub {
font-size:18px;
background-color:#e5e5e5;
font-family: arial;
}
pre {
font-family: monospace;
display: inline;
white-space: pre-wrap;
white-space: -moz-pre-wrap !important;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;
}
</style>
</head>
<body>
<table class="gridtable" border=2>
<tr><th colspan=2 class=head>
RHEVM CI Jenkins Daily Report - 21/06/2017
</th></tr><tr><th colspan=2 class=sub>
<font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Critical</a></font>
</th></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/ovirt_master_hc-system-tests/">ovirt_master_hc-system-tests</a>
</td><td>
This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/">test-repo_ovirt_experimental_master</a>
</td><td>
This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
------=_Part_662_216133554.1498086001714--
7 years, 5 months