Hey all-
I’m trying to build a new version of a package and got the aforementioned
error, but only under EPEL 8, all other builds (Rawhide, F35, F34, EPEL 9)
built fine. The failed build is at
https://koji.fedoraproject.org/koji/taskinfo?taskID=84560380.
I’m curious what I can do, but also to
Hey all-
I’m unable to build Swift on Fedora 36 and Rawhide while it does build
on F35. I’ve been able to condense the entire issue down to the
following sample code that demonstrates the problem:
nothing.S:
#define ASM_TYPE_FUNCTION(symbol) .type symbol, %function
#define ASM_SIZE(symbol) .
FWIW, I get the same result if using GCC.
On 28 Mar 2022, at 16:43, Ron Olson wrote:
Hey all-
I’m unable to build Swift on Fedora 36 and Rawhide while it does
build on F35. I’ve been able to condense the entire issue down to
the following sample code that demonstrates the problem
That was it! I somehow missed that change to the macros and undermining
_auto_set_build_flags fixed it. Thanks!
On 29 Mar 2022, at 4:38, Sérgio Basto wrote:
On Mon, 2022-03-28 at 16:43 -0500, Ron Olson wrote:
Hey all-
I’m unable to build Swift on Fedora 36 and Rawhide while it does
build on
I submitted some builds yesterday and didn’t get any emails, and at least as of
6:18 CDT every link I click on the main webpage replies with “server is
offline”.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to dev
Ah, didn’t know about that url for some reason. I’ll check there next time,
thanks.
On 1 Apr 2022, at 12:02, Kevin Fenzi wrote:
> On Thu, Mar 31, 2022 at 06:19:06AM -0500, Ron Olson wrote:
>> I submitted some builds yesterday and didn’t get any emails,
>> and at least as of 6:18
Hi all-
I got several strange messages on my update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2022-bf60d68bdc
The (multiple) messages suggest the update was ejected, but I tested an install
on a fresh image of 35 and 5.6.1 installed fine. Did I do something wrong?
Thanks,
Ron
_
ild (noarch) completed successfully
➜ ~
But I’m not clear on what this does, and should I be doing it as part of every
koji update?
On 9 May 2022, at 15:28, Mikel Olasagasti wrote:
> Hi Ron,
>
> Hau idatzi du Ron Olson (tachokni...@gmail.com) erabiltzaileak (2022
> mai. 9, al. (22
Hey all-
I got a bug report about installing Swift on RHEL 8 where nothing
provides binutils-gold. I _think_ this will fix it:
```
%if 0%{?el8}
Requires: binutils
%else
Requires: binutils-gold
%endif
```
But was hoping for some confirmation about this being the right way to
handle
No, it’s not available in RHEL nor in CentOS 8 and Stream 8; if I used the rhel
tag would that include those?
On 10 May 2022, at 10:24, Neal Gompa wrote:
> On Tue, May 10, 2022 at 11:01 AM Ron Olson wrote:
>>
>> Hey all-
>>
>> I got a bug report about installing Sw
Thank you very much Mattia!
On 10 May 2022, at 11:36, Mattia Verga via devel wrote:
> Il 10/05/22 18:30, Mattia Verga ha scritto:
>> Il 09/05/22 22:28, Mikel Olasagasti ha scritto:
>>> Hi Ron,
>>>
>>> Hau idatzi du Ron Olson (tachokni...@gmail.com) erabilt
Hey all-
I have a VM that I keep perpetually on Rawhide for testing that has working
fine with updates until the latest 5.18 kernels; it just hangs. Nothing is
shown on the screen, no kernel panics, just hangs. The VM is running on ESXi
6.0 on a X7350 Xeon (it’s a Dell PowerEdge R900 server FWI
net
installs
On Thu, May 12, 2022 at 2:15 PM Richard W.M. Jones
wrote:
On Thu, May 12, 2022 at 11:35:44AM -0500, Ron Olson wrote:
Hey all-
I have a VM that I keep perpetually on Rawhide for testing that has
working fine with updates until the latest 5.18 kernels; it just
hangs. Nothing is
Apologies in advance if this is laughable naïveté, but would a possible
solution be to have a different repo for packages compiled against the
latest-n-greatest architectures, and packagers could choose to include their
packages in there, similar to EPEL?
Packages in this hypothetical repo could
Hey all-
I’m trying to run a mock build with EPEL-8 (epel-8-x86_64) and it fails with:
[MIRROR] kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm: Status code: 403 for
https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001/non_modular/kernel-headers-4.18.0-305.3.1.e
--buildsrpm --rebuild
--rpmbuild-opts=--noclean --no-cleanup-after 2>&1 | tee
$MYDIR/mock-results/build-output.txt
On 21 Jun 2021, at 6:48, Stephen John Smoogen wrote:
> On Sun, 20 Jun 2021 at 18:25, Ron Olson wrote:
>>
>> Hey all-
>>
>> I’m trying to run a moc
Funny enough, neither did I.
On 21 Jun 2021, at 11:58, Stephen John Smoogen wrote:
> I don't know.
>
> on my systems I did a find /etc/mock/ -type f -print | xargs grep
> infrastructure.fedoraproject.org and did not have any hits.
>
> On Mon, 21 Jun 2021 at 10:35, Ron
="https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001";
> href="non_modular/kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm"/>
>
> Looking at the contents of the stuff local is giving.. it is only
> those files which are local to IA
Hey all-
I’m curious as to why submitting a new build to Bodhi takes a week to be pushed
to stable, but two weeks for EPEL-8. Is the presumption that it’s just that
much more time for folks to test and verify?
Ron
___
devel mailing list -- devel@lists
What if we used the elements from the periodic table as codenames,
starting with hydrogen and continuing on through to the end of the
(currently known) list. 118 elements, two releases a year, and we’re
good for 59 years of codenames. :)
Just a thought.
Ron
On 4 Nov 2024, at 10:32, Neal Gomp
Hey all-
Dunno if there’s a better place to ask, but as part of trying to build Swift
for EPEL 10 I’ve been running into some old issues that were resolved because
of later versions of other packages (e.g. clang, python); is there somewhere a
place that I can find what is available in EPEL 10 a
, Fabio Valentini wrote:
On Thu, Sep 19, 2024 at 5:20 PM Stephen Smoogen
wrote:
On Thu, 19 Sept 2024 at 11:07, Ron Olson
wrote:
Hi all-
I’m trying to get Swift packaged for EPEL 10 but have an
interesting situation that I presume has been seen before, so am
hoping for some guidance
Thanks very much! I’ll give that a try immediately.
On 19 Sep 2024, at 16:27, Fabio Valentini wrote:
On Thu, Sep 19, 2024 at 11:16 PM Ron Olson
wrote:
That sounds a lot easier than what I’ve been trying to do; do you
happen to have an example, or a script that shows your process so I
can
Hi all-
I’m trying to get Swift packaged for EPEL 10 but have an interesting
situation that I presume has been seen before, so am hoping for some
guidance.
Since 5.9 Swift has required a previous version of Swift to build; 5.8
is the last version that builds by itself. Now I’d like to packag
I submitted https://bugzilla.redhat.com/show_bug.cgi?id=2313425 but haven’t
heard anything; I sent him some emails but haven’t heard back.
Thanks!
Ron
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le.
Hey all,
I’ve been having difficulty building Swift on Koji’s x86_64
builders, as well as the aarch64 ones too, occasionally. The build.log
doesn’t seem to show the cause of the failure, just that a particular
command failed and thus stops the job. For example,
https://kojipkgs.fedoraproject.
Hi all-
I was able to get Swift in EPEL 10…I think; it shows on
https://bodhi.fedoraproject.org/updates/?search=swift-lang that 5.8.1 is
available on “el10_0”, while the other EPEL versions were “el9”, “el8”, etc.
Using a centos stream 10 container, I enabled CNB and epel-release, but Swift
is
Hey all-
I’m trying to fix build failures for swift-lang on F42 and while
I’ve fixed a number of places where wasn’t explicitly
defined, I’m now getting a strange compile error regarding math.h and
cmath that I can’t reproduce outside of a full build:
```
54 | #if __has_include()
55 | #in
101 - 128 of 128 matches
Mail list logo
