On 15. 04. 20 20:30, Josh Stone wrote:
On 4/15/20 11:19 AM, Miro Hrončok wrote:
I can help you setup a test that builds the packages with rpmbuild or in local
mock. However, the CI pipeline only runs on x86_64.
Can that x86_64 host still use an i686 mock?
We use it in PR workflow and we
On 4/15/20 11:19 AM, Miro Hrončok wrote:
> I can help you setup a test that builds the packages with rpmbuild or in
> local
> mock. However, the CI pipeline only runs on x86_64.
Can that x86_64 host still use an i686 mock?
___
devel mailing list --
On 15. 04. 20 20:11, Florian Weimer wrote:
Would anyone be willing to help us to set up a gating test which builds
lua, bash, ninja-build using the new glibc in Koji? (I hope this is
something the infrastructure supports.)
I can help you setup a test that builds the packages with rpmbuild or
* Vít Ondruch:
> Is this problem back?
>
>
> https://koji.fedoraproject.org/koji/taskinfo?taskID=43439516
>
> https://koji.fedoraproject.org/koji/taskinfo?taskID=43439614
Yeah, sorry, I made a mistake, rebuilding with the broken source
tarball. I realized my mistake as soon as I received mail
Is this problem back?
https://koji.fedoraproject.org/koji/taskinfo?taskID=43439516
https://koji.fedoraproject.org/koji/taskinfo?taskID=43439614
Vít
Dne 09. 04. 20 v 20:28 Florian Weimer napsal(a):
> Sorry about your troubles.
>
> I have identified the problematic upstream change, and we
Sorry about your troubles.
I have identified the problematic upstream change, and we will cease
rawhide updates of glibc until that issue is fixed.
Thanks,
Florian
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to
On 09. 04. 20 8:22, Zdenek Dohnal wrote:
I filed https://bugzilla.redhat.com/show_bug.cgi?id=1822468 on glibc, maybe they
can direct us to the right way.
It appears that it was indeed the glibc update.
After untagging it, the builds pass on 32bit.
--
Miro Hrončok
--
Phone: +420777974800
IRC:
I filed https://bugzilla.redhat.com/show_bug.cgi?id=1822468 on glibc,
maybe they can direct us to the right way.
On 4/9/20 8:12 AM, Zdenek Dohnal wrote:
> I have the same issue with vim's build:
>
> https://kojipkgs.fedoraproject.org//work/tasks/8185/43148185/build.log
>
> I did the diff of
I have the same issue with vim's build:
https://kojipkgs.fedoraproject.org//work/tasks/8185/43148185/build.log
I did the diff of installed packages between the last successful build
and the failed one and the packages which changed are:
glibc
openssl-libs
krb5-libs
qt5-srpm-macros
graphite2
On 4/9/20 6:22 AM, Jerry James wrote:
On Wed, Apr 8, 2020 at 9:57 PM Sérgio Basto wrote:
I'm having the same problem
https://koji.fedoraproject.org/koji/taskinfo?taskID=43144692
Me, too. Two packages, both failing on the 32-bit architectures due
to segfaults in find, grep, or xargs in the
On Wed, Apr 8, 2020 at 9:57 PM Sérgio Basto wrote:
> I'm having the same problem
>
> https://koji.fedoraproject.org/koji/taskinfo?taskID=43144692
Me, too. Two packages, both failing on the 32-bit architectures due
to segfaults in find, grep, or xargs in the alt-ergo case (it's hard
to tell) and
On Wed, 2020-04-08 at 19:40 -0700, Kevin Buettner wrote:
> Hi,
>
> I'm seeing some build failures for i386 and armv7hl when attempting a
> scratch build of the gdb package. These problems don't appear to be
> at all related to the problem that I was fixing. In each case, a
> segfault
> occurs
Hi,
I'm seeing some build failures for i386 and armv7hl when attempting a
scratch build of the gdb package. These problems don't appear to be
at all related to the problem that I was fixing. In each case, a segfault
occurs when running "make".
The koji task is here:
13 matches
Mail list logo
