FMN (https://apps.fedoraproject.org/notifications) is currently one of the
main blocking point for dropping fedmsg in favour of fedora-messaging.
FMN is quite important to the community and the composition of Fedora
because it gives emails and notifications on commits, composes, builds and
updates via email and other tools.
However, the code base is written in Python 2.7 and not maintained anymore.
Currently the service has to run on a Fedora 28 system to continue running.
This causes multiple problems and concerns, and needs to be addressed
before the datacenter move in June.
In order to start putting together a specification for a replacement, we
should try to look at the minimum requirements for a notification system.
For example the current system supports sending notifications to IRC,
emails and SSE (Server Sent Event), Can we live without SSE ? Can we live
without IRC ? Do we need it to monitor everything it does currently or just
a subset of items that the community has found useful.
Let's use this thread to brainstorm ideas on what we need.
Sometimes, users run into problems because they install nss_nis on
x86_64 and want to use 32-bit applications, but those do not work
correctly because nss_nis.i686 is not installed. I think we have an
opportunity here to improve the system administrator experience with
If we add this to nss_nis.spec:
Recommends: (nss_nis(x86-32) if glibc(x86-32))
then when the user installs nss_nis after glibc.i686, they will get both
packages, as expected.
Unfortunately, it does not work if nss_nis.x86_64 is installed first.
Is there a way to fix this aspect?
What would be a good way to abstract this into some RPM macro, so that
we can apply this to other plugins as well?