Release criteria proposal: networking requirements
by Adam Williamson
Hi folks!
So at this week's blocker review meeting, the fact that we don't have
explicit networking requirements in the release criteria really started
to bite us. In the past we have squeezed networking-related issues in
under other criteria, but for some issues that's really difficult,
notably VPN issues. So, we agreed we should draft some explicit
networking criteria.
This turns out to be a big area and quite hard to cover (who'd've
thought!), but here is at least a first draft for us to start from. My
proposal would be to add this to the Basic criteria. I have left out
some wikitext stuff from the proposal for clarity; I'd add it back in
on actually applying the proposed changes. It's just formatting stuff,
nothing that'd change the meaning. Anyone have thoughts, complaints,
alternative approaches, supplements? Thanks!
=== Network requirements ===
Each of these requirements apply to both installer and installed system
environments. For any given installer environment, the 'default network
configuration tools' are considered to be those the installer documents
as supported ways to configure networking (e.g. for anaconda-based
environments, configuration via kernel command line options, a
kickstart, or interactively in anaconda itself are included).
==== Basic networking ====
It must be possible to establish both IPv4 and IPv6 network connections
using DHCP and static addressing. The default network configuration
tools for the console and for release-blocking desktops must work well
enough to allow typical network connection configuration operations
without major workarounds. Standard network functions such as address
resolution and connections with common protocols such as ping, HTTP and
ssh must work as expected.
Footnote titled "Supported hardware": Supported network hardware is
hardware for which the Fedora kernel includes drivers and, where
necessary, for which a firmware package is available. If support for a
commonly-used piece or type of network hardware that would usually be
present is omitted, that may constitute a violation of this criterion,
after consideration of the [[Blocker_Bug_FAQ|hardware-dependent-
issues|normal factors for hardware-dependent issues]]. Similarly,
violations of this criteria that are hardware or configuration
dependent are, as usual, subject to consideration of those factors when
determining whether they are release-blocking
==== VPN connections ====
Using the default network configuration tools for the console and for
release-blocking desktops, it must be possible to establish a working
connection to common OpenVPN, openconnect-supported and vpnc-supported
VNC servers with typical configurations.
Footnote title "Supported servers and configurations": As there are
many different VPN server applications and configurations, blocker
reviewers must use their best judgment in determining whether
violations of this criterion are likely to be encountered commonly
enough to block a release, and if so, at which milestone. As a general
principle, the more people are likely to use affected servers and the
less complicated the configuration required to hit the bug, the more
likely it is to be a blocker.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
1 year, 9 months
Konsole missing from desktop pop-up
by Ian Pilcher
After updating to Plasma 5.23.2, Konsole is missing from the desktop
pop-up menu (what the desktop settings refers to as the "Standard
Menu").
Anyone know how to get it back?
--
========================================================================
In Soviet Russia, Google searches you!
========================================================================
2 years
Re: kf5-rpm-macros
by Neal Gompa
On Fri, Nov 26, 2021 at 9:16 PM Maxwell G <gotmax(a)e.email> wrote:
>
> Hi,
>
> I am a little unsure about the kf5 macros, specifically the ones that have exactly the same value as their non-kf5 counterparts (e.g. `%_kf5_bindir`). Are all KDE packages required to use them? I assume that packages should at least be consistent. I am asking, because I have been reviewing some KDE packages that don't use the kf5 macros consistently or even use `%{_macro}` and `%{_kf5_macro}` at different places in the same specfile. I figured that I'd ask here before correcting anybody else.
>
The main reason for the macros is that it ensures we can have
consistent, correct behavior on both Fedora and EPEL (RHEL/CentOS).
Backporting our own macros is a lot easier when they're in our own
namespace. We generally prefer KDE applications to use the qt5/kf5
macros in place of the standard ones for this reason.
--
真実はいつも一つ！/ Always, there's only one truth!
2 years
kf5-rpm-macros
by Maxwell G
Hi,
I am a little unsure about the kf5 macros, specifically the ones that have exactly the same value as their non-kf5 counterparts (e.g. `%_kf5_bindir`). Are all KDE packages required to use them? I assume that packages should at least be consistent. I am asking, because I have been reviewing some KDE packages that don't use the kf5 macros consistently or even use `%{_macro}` and `%{_kf5_macro}` at different places in the same specfile. I figured that I'd ask here before correcting anybody else.
Thanks,
Maxwell
--
Maxwell G (@gotmax23)
Pronouns: He/Him/His
PGP Key Fingerprint: f57c76e5a238fe0a628e2ecef79e4e25e8c661f8
PGP Keyserver: hkp://keyserver.ubuntu.com
gotmax(a)e.email
2 years
Wrong displayed characters
by Klaus Kolle
Dear list..
After I've upgraded my Fedora 33 to 34 last week (yes I'm behind, but so
it is) some applications doesn't show correct fonts - just squares with
small numbers inside.
Most applications seems to work but for instance the Tor browser shows
up with garbled test in the address line as in the tab - and even pop-ups.
In other applications it is in the file open/save diaglogs the text i
garbled.
It is probably a simple setting, but I can't figure out where to look.
Can you help me?
|<
--
Med venlig hilsen / Kind regards
Klaus Kolle
Teknikumingeniør, B.Sc.EE., e-mail : klaus(a)kolle.dk
Master of IT www : www.kolle.dk
Asger Jorns Vej 17 Telefon : +4522216044
DK-8600 Silkeborg, Denmark
"Man skal ikke tilskrive til sammensværgelser hvad der tilstrækkeligt
kan forklares af inkompetence"
Poul Henning Kamp
Planlægning er tanker om noget man agter at gøre en gang i fremtiden,
hvis omstændighederne tillader det.
Klaus Kolle 2006
Perfection is achieved not when nothing more to add, but when there is
nothing more left to take away.
Antoine de Saint-Exupery
2 years
plasma wayland niggles
by Chris Rouch
I've just upgrade to Fedora 35 using dnf, and tried to use wayland with
plasma.
Mostly it works well (with F34 plasma wayland was nearly unusable for me),
but there are a couple of small problems.
I have a bash script set to run on startup, which invokes various
applications and puts them in the background, and then exits. On X11 the
applications keep running, on wayland they also exit. I found the fix was
to add "wait" at the end of the script.
They shortcut keyboard mapping for the numeric keypad is broken, so that if
I use KP_UP on the numeric keypad, the UP key is also mapped. I'm not sure
if this is a feature or a bug. On X11 they are treated as different.
The python gtk FileChooserDialog is strange. With the code here:
https://python-gtk-3-tutorial.readthedocs.io/en/latest/dialogs.html on X11
the buttons are shown in the expected colours at the bottom. On wayland
they are dark on black and shown at the top.
Regards,
Chris
--
Met vriendelijke groet,
Chris Rouch
2 years
