Last meeting we discussed whether we should change to GPT as default partitioning. Now some of our members have submitted a change proposal to make GPT the default partitioning for new installations. I think this is actually long overdue, yet better communication among us would actually be nice as well.
I don’t know if there is a potential problem. Some time ago, if I remember correctly it was Neil who wrote in a discussion about storage that a software RAID is no longer possible, because - so my memory - the biosboot partition is not replicable over multiple disks. So if the previous boot disk fails, you can't just boot from another disk.
I never checked it and didn’t read the technical specification. And all our server have hardware raid. So, does anybody knows about it in detail?
I just published the article "Setting up dnsmasq - a lightweight DHCP and DNS server“ (https://docs.fedoraproject.org/en-US/fedora-server/sysadmin-dnsmasq/). Unfortunately, until now nobody had picked it up for review. So it does get under the rule no objection is considered consent, unfortunately.
Nevertheless, it is never too late for a review. It would be great it someone would take it.
it finally happened. Fedora 36 is out of the door, after all the stumbling blocks along the way.
I pushed the latest releases of our documentation upstream, as far as they needed an update for F36. After the docs site updates again, it will be online. Probably in an hour or so.
Nevertheless, I think we should polish our review process.
Just as an info: In cooperation with the docs team and especially thanks to the efforts of darknao, our noticeability is greatly improved.
On the download page
there is now a new footer directly below the download links with links to our documentation, support and chat.
The same is true for the overview page,
down below all the descriptions.
Many thanks to Francois Andrieu (darknao)
In our meeting x3mboy raised the question if we should start to migrate our repo to GitLab as many projects do. We decided to open a discussion on the mailing list.
So, the floor is open.
My opinion: IMHO, pagure does for us what we need at the moment. Therefore, there is no need for us to migrate now. And we have so many task to (see https://pagure.io/fedora-server/boards/Works%20in%20progress) we are well advised to concentrate on those. Not only, that one has to do the work, all others have to adapt there working routine and maybe spend some time to learn the new / different functionality. We should better spend the time into our working projects.
We have still to determine our goals for F37.
One topic we have to care about is an open bug/rfe, we already postponed.
We decided to continue our discussion on mailing list. Among other things, we still disagreed a bit on how to judge z-shell.
I think we should really review server DVD content. It was basically created a decade ago, presumably with various adjustments in the meantime. But we have some unresolved issues about it still open.
Hey folks! Please see attached. Due to some late-breaking blockers and
fixes, we're now up to RC5 for F36 Final. Go/no-go is tomorrow. If
folks can help with testing, that'd be great.
Here's a quick summary of the changes between the RC composes:
RC1 -> RC2
gtk4-4.6.2-3.fc36 to fix #2071228
clevis-pin-tpm2-0.5.2-1.fc36 rust-tpm2-policy-0.6.0-1.fc36 to fix FTBFS
RC2 -> RC3
wpa_supplicant-2.10-4.fc36 to fix #2072070
tracker-miners-3.3.0-2.fc36 to fix #2079308
mutter-42.0-6.fc36 to fix #2081070
openssl-3.0.2-4.fc36 to fix #2069239
gzip-1.11-3.fc36 to fix #2073312
kernel-5.17.5-300.fc36 for #2080694
snapper-0.10.1-1.fc36 for FTBFS
selinux-policy-36.8-1.fc36 for #2065940
livecd-tools-30.0-1.fc36 for #2007045
xz-5.2.5-9.fc36 for #2080938
xdg-desktop-portal-1.12.4-1.fc36 for #2060990
sssd-2.7.0-1.fc36 for #2077856
gr-osmosdr-0.2.3-21.20210217gita100eb02.fc36 to fix FTBFS
RC3 -> RC4
firefox-100.0-2.fc36 for #2081488
RC4 -> RC5
sushi-41.2-1.fc36 for #2067969
gnome-photos-42.0-2.fc36 for #2079344 #2081291
aws-2020-7.fc36 matreshka-20.1-10.fc36 templates_parser-11.8.0-30.fc36 for FTBFS
So, RC3 had quite a lot of change in it. RC4 and RC5 are much more
limited. So we can count most tests from RC3 or later as being valid
for RC5; tests of Firefox, Nautilus and GNOME Photos should be re-
I have transferred results from RC3 and RC4 to RC5 in the matrix where
appropriate, leaving out things that are considered 'sanity tests'
(basic boot and install tests) which we try to run on every compose to
rule out some kind of cosmic bit-flip unexpectedly breaking an image.
So any spaces left on Basic/Beta/Final tests are ones we should try to
Special note on the Active Directory tests: it looks like tflink and
sgallagh ran these on RC1, thanks a lot. Since we did get a new sssd
between then and RC5 it would be *nice* if we could run them again, but
if not we can probably run with the RC1 results in the end.
Thanks again everyone!
IRC: adamw | Twitter: adamw_ha