Hi,
I found this issue when installing fedpkg in either f25 container or
VM. There are two koji versions in f25 repos, following steps run in a
f25 container
[root@e151b05870c7 pkgs]# dnf repoquery koji
Last metadata expiration check: 0:01:39 ago on Sat Aug 12 02:25:14 2017.
koji-0:1.10.1-13.fc25
Hi,
Michal Novotny wrote:
> - "Follow Fedora branching" project switch that (if enabled) makes COPR
> fork your rawhide chroots into the newly branched ones
> and hence user will have your packages available in their f27 systems
> and they will also be available for your upcoming builds
> (meaning
Hi Zbyszek,
On Wed, Aug 9, 2017 at 12:14 AM, Zbigniew Jędrzejewski-Szmek
wrote:
...
> athmanepython-fluidity-sm python-lexicon python-pybloomfiltermmap
Fixed in rawhide, they were using the old python3 guidelines (ie:
without special macros)
BR.
___
On Thursday, 10 August 2017 at 12:29, Richard W.M. Jones wrote:
> Never mind. Something in the atlas build segfaults when building
> on ppc64le:
>
> https://koji.fedoraproject.org/koji/taskinfo?taskID=21145734
>
> This is a mess :-(
Just switch to openblas already. ;)
I'd propose a Change for
On 08/11/2017 09:57 AM, Pierre-Yves Chibon wrote:
> On Fri, Aug 11, 2017 at 10:17:59AM -, Martin Gansser wrote:
>> for f27: This is a known problem see:
>> https://pagure.io/fedora-infrastructure/issue/6236
>> They working on it right now.
>>
>> f26 works for me now with:
>> $ git checkout -b
Greetings developers,
I just submitted a review request [1] for kcov [2] that I recently
discovered. It has no relation to Linux's kcov and is more akin to
lcov, except that all it needs is a binary with DWARF debuginfo
instead of requiring compile-time instrumentation.
I came across kcov when I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
===
#fedora-meeting: FESCO (2017-08-11)
===
Meeting started by sgallagh at 16:01:00 UTC. The full logs are available
athttps://meetbot.fedoraproject.org/fedora-meeting/2017-08-11/fesco
On 08/11/2017 02:02 AM, Panu Matilainen wrote:
>
> The full story is in https://bugzilla.redhat.com/show_bug.cgi?id=1480407
> but to summarize, this is actually a bug in rpm 4.13.x which is not
> ignoring unknown signature header tag like it should, older rpm versions
> are not affected. Also the
On Thu, Aug 10, 2017 at 8:18 PM Stephen Gallagher
wrote:
> Following is the list of topics that will be discussed in the
> FESCo meeting Friday at 16:00UTC in #fedora-meeting onirc.freenode.net.
>
> To convert UTC to your local time, take a look at
> http://fedoraproject.org/wiki/UTCHowto
>
> o
On Fri, Aug 11, 2017 at 10:17:59AM -, Martin Gansser wrote:
> for f27: This is a known problem see:
> https://pagure.io/fedora-infrastructure/issue/6236
> They working on it right now.
>
> f26 works for me now with:
> $ git checkout -b f26; git push --set-upstream origin f26; fedpkg build
>
On Fri, Aug 11, 2017 at 04:55:34AM -0400, Jaroslav Skarvada wrote:
>
> I see the following when pushing to new repo:
>
> $ fedpkg push
> /usr/lib/python2.7/site-packages/fedora/client/bodhi.py:48:
> DeprecationWarning: fedora.client.bodhi has been deprecated. Please use
> bodhi.client.bindings
Hello,
I reported the same incident just after F24->F25 upgrade and it was
rectified rather quickly.
Now it happens again after the F25->F26 upgrade.
When entering one's password to dismiss the screen lock the fingerprint
reader is flashing which seems ok.
However after entering the passwo
Hello,
I am sending these release notes also to fedora-devel list (and not just
copr-devel list as usually) because they contain information
about upcoming Fedora branching and what features COPR provides to move the
set of packages from your rawhide chroots into the newly branched ones.
We have
On 7 August 2017 at 15:35, Dennis Gilmore wrote:
> [3] https://kojipkgs.fedoraproject.org/mass-rebuild/f27-failures.html
>
This file seems suspiciously small... I somehow don't believe that there
were "0 failed builds" :-)
--
Mat Booth
http://fedoraproject.org/get-fedora
__
for f27: This is a known problem see:
https://pagure.io/fedora-infrastructure/issue/6236
They working on it right now.
f26 works for me now with:
$ git checkout -b f26; git push --set-upstream origin f26; fedpkg build --nowait
on f25 branch: I don't know what happens.
$ git push --set-upstream
Ambassadors and members of Fedora community,
unfortunately I have to cancel the Elections to FAmSCo due to a
mistake made in configuration of Voting machine. Today (Friday)
morning I received an email reporting issue where people who are not
members of "ambassadors" group in FAS can not vote. Quic
On 08/11/2017 03:44 AM, Kevin Fenzi wrote:
Sadly we ran into a problem...
as soon as the new rpm was in the rawhide buildroot and builds were made with
it, things started piling up in f27-pending (the tag things land in after build
so the autosigner can sign them and move them to f27).
It see
- Original Message -
> On 08/10/2017 03:01 PM, Fabio Valentini wrote:
> > I've just pushed an import commit to my first repository that was created
> > with fedrepo_req on pagure, and I got the following traceback from the
> > remote when it obviously failed to run a post-receive hook:
>
In addition to new package not building because of tag, by following the
https://fedoraproject.org/wiki/Join_the_package_collection_maintainers#Import.2C_commit.2C_and_build_your_package
On step:
fedpkg switch-branch BRANCH
Gives:
$ fedpkg switch-branch f26
/usr/lib/python2.7/site-packages/fedo
19 matches
Mail list logo
