Intel's Clear Linux optimizations
by František Zatloukal
Hi,
Phoronix recently release article[1] about Intel's Clear Linux with some
cool graphs showing nice performance gain compared to Xubuntu.
I didn't have time to dig in and look how it's performing against Fedora,
but I'd assume Fedora can be compared to Xubuntu in terms of compiler
settings.
I think i'll be interesting to look into it and find out if Fedora can't
tweak compiler settings (eg use LTO for critical things like Mesa, Kernel,
...). I think it could be interesting fo Fedora users to have this enabled
if there are not any disadvantages other than compile time, compile memory
usage and so on.
What do you think?
[1]
http://www.phoronix.com/scan.php?page=article&item=intel-clr-opengl&num=1
--
Best regards / S pozdravem,
František Zatloukal
Project Coordinator
Red Hat
5 years, 1 month
Orphaning pl (SWI Prolog)
by Petr Pisar
I have no interest in maintaining pl (SWI Prolog) package and thus I'm
going to orphan it.
The package is a Prolog langugage interpreter with bundled various
libraries and tools written in that language. E.g. an HTTP server or an
interface to Java virtual machine.
Upstream does a new major release roughly every year and a few bug-fix
releases during the year.
From packaging point of view there are few downs like:
Reviewing each rebase for licenses is tiresome due the size (118 MB).
Upstream does not like how it is packaged because Fedora bends it to FHS.
Fedora does not like how it is packaged because it's not bended enough.
There are occasional FTBFS when JVM reorganizes its files.
The package should be renamed to swipl to match the upstream.
The source archive is stripped down from non-free files.
The pl package has two comaintainers, mef and bagnara, who did not touch the
pacakge for last 10 years.
The package is required when building and running these source packages:
perl-Language-Prolog-Yaswi ppisar,jplesnik Can be removed.
ppl bagnara,pcpa A subpackage can be disabled.
python-pyswip thofmann A subpackage can be disabled.
The package builds fine now and a new 8.1 release is waiting for
packaging.
If you want to take over a maintainership of this package, let me know
and I will assign it to you. Otherwise I will orphan it next week.
-- Petr
5 years, 1 month
Qt file dialogs under GNOME and MATE
by Alexander Ploumistos
Hello,
While ironing out the kinks in the upcoming version of Molsketch with
the upstream developer, we noticed that we weren't seeing the same
dialogs. He is on KDE (OpenSuSE) and I was testing in GNOME and MATE.
Molsketch has an option to save a single molecule/structure with the
.msk extension. Under KDE, the extension appears in the file dialog
and is automatically appended to the file name. This does not happen
under GTK.
He installed Fedora in a VM and ran some tests:
> Now for the file extensions: the filter I pass to the "save file" dialog is
> "Molsketch default (*.msk *.msm)". On my system (KDE, OpenSUSE 15.0 or 42.3,
> depending on the machine), this is shown as "Molsketch default" and there is a
> checkbox for appending the default extension (.msk). For the "save a molecule"
> dialog, the same applies for ".msm". Now, when I try the same thing on Fedora
> (Gnome, I guess), it also shows "Molsketch default" (so, without the
> extension) for the filter in the dialog. When I save something, however, it
> does not add any extension. Comparing that to the default text editor (gedit),
> this seems to be expected behavior: I can select "All Text Files" and there
> will be no extension appended (on the other hand, that really seems to be what
> the filter selects -- not *.txt, as I would have expected). In LibreOffice, it
> seems that the extension is shown in the filter text and appended to the name
> if no extension is given. On my system, I can simply pass "Molsketch default
> (*.msk) (*.msk *.msm)" to have "Molsketch default (*.msk)" displayed. On
> Fedora, this seems to get converted to "Molsketch default", however.
>
> Oh, and the "add '*.msk' automatically" functionality worked due to a bizarre
> piece of code that disassembled the filter string and thus extracted the
> extension. That was added if no extension was given in filename returned by
> the dialog. Should that happen instead (of course without the awkward parsing
> of the filter)?
>
> I'm a little confused here by the difficulties to use the native save dialog
> via Qt. Any suggestions?
Can anyone help with this?
All the best,
Alex
5 years, 1 month
undefined symbol: shm_open (ppc64le and aarch64)
by Tom Callaway
One of my packages failed the mass rebuild, but only on ppc64le and
aarch64. The error they both hit is this:
Error: package or namespace load failed for 'BiocParallel' in
dyn.load(file, DLLpath = DLLpath, ...):
unable to load shared object
'/builddir/build/BUILDROOT/R-BiocParallel-1.16.5-1.fc30.ppc64le/usr/lib64/R/library/BiocParallel/libs/BiocParallel.so':
/builddir/build/BUILDROOT/R-BiocParallel-1.16.5-1.fc30.ppc64le/usr/lib64/R/library/BiocParallel/libs/BiocParallel.so:
undefined symbol: shm_open
Error: loading failed
Here's the linker invocation:
g++ -m64 -std=gnu++11 -shared -L/usr/lib64/R/lib -Wl,-z,relro
-Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld
-o BiocParallel.so ipcmutex.o -L/usr/lib64/R/lib -lR
Now, google says this might be due to a lack of -lrt, but what's not
clear to me is why it only fails on these two architectures (I've
confirmed that none of the others have -lrt either).
Full build logs are here:
https://koji.fedoraproject.org/koji/taskinfo?taskID=32581444
Thanks in advance,
~tom
5 years, 1 month
F30 Self-Contained Change proposal: Improved GRUB menu
by Ben Cotton
https://fedoraproject.org/wiki/Changes/ImprovedGrubMenu
== Summary ==
Improve the GRUB menu by only having the default boot option for each
installed operating system in the main menu, and the other options
into a sub-menu. This would better organize the boot options and lead
to an easier and seamless boot experience.
== Owner ==
* Name: [[User:Javierm|Javier Martinez Canillas]]
* Email: javierm(a)redhat.com
== Detailed Description ==
The current GRUB menu is confusing, specially when multiple operating
systems are installed. The Fedora boot entries are added first and
then the ones for the other installed operating systems.
The main menu contains all the boot entries for Fedora but only the
default boot entry for the other operating systems, the non-default
boot entries for the other installed operating systems are placed into
a per operating system sub-menu.
An example of how the GRUB menu currently looks can be found at
[https://javierm.fedorapeople.org/grub2/menu/fedora_menu.png
https://javierm.fedorapeople.org/grub2/menu/fedora_menu.png]
This can be improved by adding a sub-menu for the Fedora non-default
boot entries, as is already the case for the other installed operating
systems. This will make the boot entries for all the operating systems
consistent.
Another improvement would be to group all the default options for the
operating systems as one section, followed by another section that
groups all the sub-menus for the non-default options.
A tentative design made by Allan Day for the improved GRUB menu can be
found at [https://wiki.gnome.org/Design/OS/BootOptions#Tentative_Design
https://wiki.gnome.org/Design/OS/BootOptions#Tentative_Design]
For Fedora, the boot option in the main menu will either be the
selected default boot entry or if no default was chosen, the latest
installed kernel. For the other installed operating systems, the boot
option in the main menu will be the latest kernel as found by GRUB's
os-prober script.
== Benefit to Fedora ==
Making the menu less confusing and with better organized boot options
will lead to a better user experience and make easier for users to
choose the operating systems to boot.
== Scope ==
* Proposal owners:
# Change GRUB to implement the changes as described in the "Detailed
Description" section.
# Make sure this is all properly documented in release-notes, etc.
* Other developers:
# Test and watch for regressions.
* Policies and guidelines: The policies and guidelines do not need to
be updated.
* Trademark approval: No changes needed.
== Upgrade/compatibility impact ==
The changes are in the grub.cfg file generated at install time by
Anaconda. Users can manually enable this after an upgrade by executing
gru2-mkconfig to regenerate their grub.cfg file.
== How To Test ==
# Single OS test
## Install Fedora in a VM.
## On boot the default boot option is in the main menu and the other
options (e.g: rescue boot option) are in a sub-menu.
# Multi boot test
## Install Fedora on a machine which other operating system installed.
## On boot the default boot options for the operating systems are in
the main menu and the other options in sub-menus.
== User Experience ==
A simpler and easier to understand GRUB boot menu. Choosing which
operating system to boot should be simpler and involve less steps.
== Dependencies ==
None
== Contingency Plan ==
* Contingency mechanism: Revert the GRUB changes.
* Contingency deadline: Beta Freeze
* Blocks release? No
* Blocks product? None
--
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapolis
5 years, 1 month