Fedora-40-20240217.n.0 won't install
by Ian Laurie
I'm guessing this is a known issue but using
Fedora-Everything-netinst-x86_64-40-20240217.n.0.iso to install an Xfce
workstation as a VirtualBox VM resulted in an aborted installation.
Error was:
===
The following error occurred while installing the payload. This is a
fatal error and the installation will be aborted.
An error occurred during the transaction: Error in POSTIN scriptlet in
rpm package dbus-common
===
Fedora-Everything-netinst-x86_64-Rawhide-20240216.n.0.iso from the
previous day gives the same error.
As a sanity check I installed Fedora 39 from
Fedora-Everything-netinst-x86_64-39-1.5.iso and it worked.
--
Ian Laurie
FAS: nixuser | IRC: nixuser
TZ: Australia/Sydney
1 month, 3 weeks
libgsystem FTBFS (Issue 2225969)
by Jeffrey Walton
Hi Everyone,
libgsystem is not building from source for F39 and F40. Cf.,
<https://bugzilla.redhat.com/show_bug.cgi?id=2225969>.
The problem seems to stem from glibsystem-devel. libgsystem adds a
step in its build process when glibsystem-devel is installed (the
GISCAN below). If glibsystem-devel is not installed, then step is
skipped (no GISCAN) and no error occurs.
CCLD libglnx.la
CCLD libgsystem.la
GISCAN GSystem-1.0.gir
src/gsystem-glib-compat.h:34: Warning: GSystem:
symbol='g_clear_pointer': Skipping foreign symbol from namespace Gio
/builddir/build/BUILD/libgsyst
em-2015.2/tmp-introspectlvqqyft1/GSystem-1.0.c:
In function ‘dump_properties’:
/builddir/build/BUILD/libgsystem-2015.2/tmp-introspectlvqqyft1/GSystem-1.0.c:229:7:
error: ISO C90 forbids mixed declarations and code
[-Werror=declaration-after-statement]
229 | const GValue *v = g_param_spec_get_default_value (prop);
| ^~~~~
The fix is easy. However, tmp-introspectlvqqyft1/GSystem-1.0.c uses a
random directory name, so we can't really provide a patch since the
name is a moving target.
Fedora's bug tracker does not have a glibsystem component to file the
bug against.
How to proceed?
Thanks in advance.
2 months
reversible dual-boot test station
by Chris Murphy
Hi,
I mentioned this in a QA meeting, and have given it enough testing that I think it's broadly usable. If desired it can be copied out of my user account and put up somewhere where QA folks will see it and can modify it as issues or improvements are discovered.
What is it? The idea is to produce a system that can confidently be used for baremetal testing, without risking the primary operating system. While VM's are a great way to test, it's also a really idealized environment that tends to not expose an assortment of bugs that affect particular hardware. But then quite a lot of folks reasonably don't want to upgrade their daily use hardware early on, because they don't want to always have to debug things, or have to figure out how to undo the upgrade if it really goes badly.
Therefore, I present a dual-boot setup offering:
* no re-partitioning;
* no installation step, instead system upgrade is used;
* reversibility, or undoability, i.e. with just a few steps you can delete the "test OS".
https://fedoraproject.org/wiki/User:Chrismurphy/Draft/dualboot_teststation
--
Chris Murphy
2 months