Disabling build options for SSE on non-capable arches ?
by David Timms
Hi, (this is a 4th retry, now trying devel as first try to packaging a
week ago says held by moderator, but doesn't seem to have been posted to
the list, and I don't know why...)
Audacity has had the following as part of rpm spec in the %configure
section:
%configure \
--disable-dynamic-loading \
...
%ifnarch %{ix86} x86_64
--disable-sse \
%else
%{nil}
%endif
Which fails on: non x86 arches:
https://koji.fedoraproject.org/koji/taskinfo?taskID=29513664
If I remove the conditional, I get successful build, but not optimized
on x86 with SSE.
What's wrong with this conditional ?
Cheers, David
5 years, 8 months
Intent to orphan coan
by Jonathan Underwood
Hi,
I am planning to orphan the coan package in a week or so unless someone
else is interested in taking on the package.
"Coan is a software engineering tool for analysing preprocessor-based
configurations of C or C++ source code. Its principal use is to simplify a
body of source code by eliminating any parts that are redundant with
respect to a specified configuration. Dead code removal is an application
of this sort." (from the project website).
Coan is somewhat dead upstream. I have just finished some housekeeping on
the package - making it build again on Fedora 29+ (with the dropping of
/usr/bin/python from the python2 package), and added a patch that was
causing crashes on Fedora 28+.
The software could do with some attention to fix these issues:
1) At present the test suite fails on arm and ppc64le
2) Various C++11 deprecation warnings are present during the building
I don't have the time to continue maintaining this package, unfortunately.
Please get in touch if you want to maintain the package and I'll hand it
over to you.
Cheers,
Jonathan
5 years, 8 months
Fedora 29 Beta status: RC5 incoming, purpose
by Adam Williamson
Hi, folks!
So, Beta RC4 is out there and being tested (thanks for all the testing
so far). There is an RC5 coming too: here's why.
We haven't found any blockers in RC4 yet, but we did find several not-
quite-blockers that seemed bad. First of all, the Silverblue (formerly
known as Atomic Workstation) installer image build failed due to a
network blip, so RC4 does not have that image. If we ship RC4 as the
Beta, we wouldn't have a Silverblue installer for the Beta at all
(unless we did some ugly hack to stuff some other image in), and that
seems bad - the image isn't release-blocking, but it is a major area of
development and we really ought to include it in Beta.
Beyond that, we happened to run into and find fixes for quite a slew of
bugs in gnome-shell, plus a couple in gtk+ and mesa that are quite
visible too. Here's a list of all the bugs in question:
https://bugzilla.redhat.com/show_bug.cgi?id=1630134
https://gitlab.gnome.org/GNOME/gnome-shell/issues/574
https://gitlab.gnome.org/GNOME/gnome-shell/issues/539
https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/227
https://gitlab.gnome.org/GNOME/gnome-shell/issues/523
https://bugzilla.redhat.com/show_bug.cgi?id=1631068
https://bugzilla.redhat.com/show_bug.cgi?id=1628462
So nirik, mboddu and I agreed it'd be reasonable to run a Beta RC5 to
give us at least the option of shipping a compose with the Silverblue
image and fixes for all those bugs, if everything goes well. As there
aren't any outright blockers in it, Beta RC4 is still a candidate for
release too.
Beta RC5 should complete in ten hours or so. There should be no
difference between Beta RC4 and Beta RC5 outside of GNOME and the mesa
fix, so most RC4 tests should be valid for RC5 too.
So, please continue testing RC4. Once RC5 arrives, go ahead and test
that too, prioritizing smoke tests, tests of GNOME, and any Basic /
Beta tests not yet run against RC4. It is not a high priority to run
tests on RC5 that have already been run on RC4, unless they're basic
smoke tests or GNOME tests.
Thanks a lot, everyone!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
5 years, 8 months