So I am getting the following becasue arduino-builder is a golang
project and apparently Go is not in ppc64 repos. Do anyone know if
golang will eventually be available on this arch?
If not, is it correct to put BOTH BuildArch: noarch and ExclusiveArch:
%{go_arches} in the arduino spec file so it
It looks like the mass rebuild completed. However I have quite a few
packages which failed because of the ppc64le / binutils(?) /
"localentry:0" thing. Are we going to do another mass rebuild to fix
this?
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
R
On Mon, Jul 31, 2017 at 9:38 AM, Richard W.M. Jones wrote:
>
> It looks like the mass rebuild completed. However I have quite a few
> packages which failed because of the ppc64le / binutils(?) /
> "localentry:0" thing. Are we going to do another mass rebuild to fix
> this?
Yes, I believe the pl
On Mon, Jul 31, 2017 at 09:42:00AM +0100, Peter Robinson wrote:
> On Mon, Jul 31, 2017 at 9:38 AM, Richard W.M. Jones wrote:
> >
> > It looks like the mass rebuild completed. However I have quite a few
> > packages which failed because of the ppc64le / binutils(?) /
> > "localentry:0" thing. Are
Hello Fedora people,
please let me remind you of the running Nomination period.
For FESCo we have opened 4 seats:
https://fedoraproject.org/wiki/Development/SteeringCommittee/Nominations
For Council we have opened 1 seat:
https://fedoraproject.org/wiki/Council/Nominations
For FAmSCo we have ope
- Original Message -
> From: "Gianluca Sforna"
> To: "Development discussions related to Fedora"
>
> Sent: Monday, July 31, 2017 10:02:55 AM
> Subject: Golang in PPC64
>
> So I am getting the following becasue arduino-builder is a golang
> project and apparently Go is not in ppc64 r
Hi packagers,
Just before the mass rebuild some debuginfo/source improvements were
enabled by default (%_debugsource_packages and %_debuginfo_subpackages).
See https://pagure.io/releng/issue/6863 and
https://fedoraproject.org/wiki/Changes/SubpackageAndSourceDebuginfo for
some background.
It didn'
Hello,
My name is Robert-André and I'm looking to become a packager for Fedora.
I'm 33 years-old Frenchman. I first tried GNU/Linux in the late 90
with Debian and what was
then Mandrake. Back then with no Internet, I remember It was tough to
get set up and find
help. After a Windows period, I got
On 31 July 2017 at 05:19, Björn Persson wrote:
> Mathieu Bridon wrote:
>> On Mon, 2017-07-31 at 00:02 +1000, Nick Coghlan wrote:
>> > So that's effectively a hard design constraint for me: folks
>> > targeting EL6 and EL7 *are* going to have to use "/usr/bin/python" in
>> > their shebang lines (s
Is there are debuginfo repository matching the contents of the f27-build
buildroot repository?
This would be extremely helpful for verifying the presence of .gdb_index
sections in separate debugging information.
Thanks,
Florian
___
devel mailing list --
The Modularity team has published a first round of Boltron feedback:
https://docs.pagure.org/modularity/prototype/boltron/feedback.html
Feedback is still being collected using the Boltron Walkthrough and UX
feedback form: http://bit.ly/mod-walkthrough
--
Adam Šamalík
---
On 31 July 2017 at 05:40, Björn Persson wrote:
> Gerald Henriksen wrote:
>> On Fri, 28 Jul 2017 21:06:45 +0200, you wrote:
>> >Why is not providing /usr/bin/python more use hostile? Why is it better
>> >for any script to use /usr/bin/python instead of /usr/bin/python3?
>>
>> Because any user of F
There will be an outage starting at 2017-08-04 21:00 UTC, which will last
approximately 15 hours.
To convert UTC to your local time, take a look at
https://fedoraproject.org/wiki/UTCHowto
or run:
date -d '2017-08-04 21:00 UTC'
Reason for outage: important HyperKitty database schema change
Af
On 31 July 2017 at 05:10, Stephen John Smoogen wrote:
> If I am writing it as /bin/sh I am expecting that bash, zsh, etc are going
> to fall into POSIX conformant mode outlined many years ago. Then the script
> I run should work on everything from that SunOS-4.1.1 box needed for a 30
> year old ex
On Mon, Jul 31, 2017 at 01:16:29PM +0200, Mark Wielaard wrote:
> = -debugsource generation fails with
> error: Empty %files file
>
> Caused by rpm/find-debuginfo.sh/debugedit being unable to find any
> source files for the generated .debug files. This could be seen as a
> packaging bug. Most lik
Hello Robert and welcome to Fedora!
Regards,
Charalampos Stratakis
Software Engineer
Python Maintenance Team, Red Hat
- Original Message -
From: "Bob Mauchin"
To: devel@lists.fedoraproject.org
Sent: Monday, July 31, 2017 1:34:23 PM
Subject: Introduction/looking for a sponsor
Hello,
M
On Mon, Jul 31, 2017 at 01:47:28PM +0200, Adam Samalik wrote:
> The Modularity team has published a first round of Boltron feedback:
> https://docs.pagure.org/modularity/prototype/boltron/feedback.html
From what I've seen on social media, response is largely positive.
Congratulations everyone! (An
I rebuilt all immediately problematic packages which use pthread_ and
clock_ functions and had the ppc64le optimization, except kernel (which
will be fixed by the upgrade to kernel-4.13.0-0.rc3.git0.1.fc27) and
community-mysql (which ran into an apparently known issue related to
unstable test cases
On 07/31/2017 05:08 PM, Florian Weimer wrote:
> I rebuilt all immediately problematic packages which use pthread_ and
> clock_ functions and had the ppc64le optimization, except kernel (which
> will be fixed by the upgrade to kernel-4.13.0-0.rc3.git0.1.fc27) and
> community-mysql (which ran into an
Missing expected images:
Workstation live i386
Server boot i386
Kde live i386
Failed openQA tests: 27/137 (x86_64), 3/18 (i386), 1/2 (arm)
New failures (same test did not fail in Rawhide-20170729.n.1):
ID: 125754 Test: x86_64 Workstation-boot-iso install_default
URL: https://openqa.fedorap
ok, I rebuilt the following ones. The ones with F next to them failed to
build:
autotrace-0.31.1-44.fc26.src.rpm
converseen-0.9.6.2-1.fc27.src.rpm
dmtx-utils-0.7.4-2.fc27.src.rpm
drawtiming-0.7.1-20.fc26.src.rpm
F gtatool-2.2.0-4.fc27.src.rpm
imageinfo-0.05-25.fc26.src.rpm
inkscape-0.9
To necromance this old thread, I wanted to give a heads up that we're about to
get a cool feature in Bodhi in response to this thread:
https://github.com/fedora-infra/bodhi/pull/1678
With that pull request, there will be a new request state called "batched".
When non-priority[0] updates reach t
Dear all,
You are kindly invited to the meeting:
Modularity Office Hours on 2017-08-01 from 10:00:00 to 11:00:00 US/Eastern
At https://meet.jit.si/fedora-modularity
The meeting will be about:
This is where you ask the Fedora Modularity Team questions (and we try to
answer them)!
Join us o
The Nomination period of Elections to Council [1], FESCo [2] and
FAmSCo [3] is now over.
The list of nominees follows:
== Council (1 open seat) ==
* Justin W. Flory (jwf / jflory7)
* Langdon White (langdon)
* Nick Bebout (nb)
* Dennis Gilmore (dgilmore / ausil)
* Till Maas (tyll / till)
== FESCo
On Mon, Jul 31, 2017 at 05:12:41PM +0200, Florian Weimer wrote:
>
> Mmph, I forgot to mention two more things:
>
> If you still see localentry:0 build failures after this, please send me
> mail with a link to the build log. This should not happen.
>
hi,
It seems issue persists for rdma-core pp
On Mon, Jul 31, 2017 at 09:34:24PM -, Randy Barlow wrote:
> request:stable. Then they will continue on as they do today. This
> should help us to reduce the daily churn of Fedora updates for
> end-users to only be updates they truly need. It may also make the
> masher be a little faster on 6 da
On Mon, 2017-07-31 at 21:00 -0400, Matthew Miller wrote:
> This is awesome, Randy! Thanks!
Caleigh did the hard work ☺
signature.asc
Description: This is a digitally signed message part
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscr
On Mon, Jul 31, 2017 at 5:34 PM, Randy Barlow
wrote:
> To necromance this old thread, I wanted to give a heads up that we're about
> to get a cool feature in Bodhi in response to this thread:
>
> https://github.com/fedora-infra/bodhi/pull/1678
>
> With that pull request, there will be a new reque
On Mon, 2017-07-31 at 22:13 -0400, Ben Rosser wrote:
> 1. Are you saying that this feature will be *activated* once it's
> merged, or just that it will be available should Fedora decide to
> turn
> it on as a policy decision? I'm assuming it's the latter, as I don't
> think I've seen a change propo
On Mon, Jul 31, 2017 at 10:51 PM, Randy Barlow
wrote:
> It would be activated whenever the Bodhi that has it is deployed.
> However, it won't be a forced policy - developers will still be free to
> click "push to stable" if they please. The autokarma feature will
> simply move updates to batched n
On 08/01/2017 02:56 AM, Honggang LI wrote:
> On Mon, Jul 31, 2017 at 05:12:41PM +0200, Florian Weimer wrote:
>>
>> Mmph, I forgot to mention two more things:
>>
>> If you still see localentry:0 build failures after this, please send me
>> mail with a link to the build log. This should not happen.
From ec47fc7c146915a775113512060cbce96d4c01f7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Petr=20P=C3=ADsa=C5=99?=
Date: Tue, 1 Aug 2017 07:36:38 +0200
Subject: Correct changelog entries
---
perl-Pod-Coverage.spec | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/perl-Pod-Co
Hi all,
Last night on IRC we were discussing the curious case of lib389. I think
this is a discussion we should have at some point.
The question really boils down to - "is lib389 a seperate project? Or is
it part of 389-ds-base?"
There are some pros and cons to both view points.
lib389 is a py
There is no debug repos for the buildroot repos.
Dennis
On 31 July 2017 6:45:24 am GMT-05:00, Florian Weimer wrote:
>Is there are debuginfo repository matching the contents of the
>f27-build
>buildroot repository?
>
>This would be extremely helpful for verifying the presence of
>.gdb_index
>sect
34 matches
Mail list logo
