Join the Rawhide Test Days: Help Shape the Future of Fedora Linux!

[Sumantro Mukherjee]

Dear Fedorans,

Are you ready to make a difference in the world of Fedora Linux? We're
thrilled to announce the launch of our brand new test day series:
Rawhide Test Days! These events are your opportunity to play a crucial
role in ensuring the quality and reliability of upcoming Fedora
releases. Rawhide test days will play their unique role in keeping
Fedora Linux releases on time.

Fedora test days are renowned for their inclusivity – they welcome
participation from both seasoned Fedora contributors and newcomers
alike. If you've been itching to dip your toes into the world of
Fedora Linux contribution, this is your perfect starting point.

For some time now, we've been dedicated to elevating the quality
standards of Fedora by implementing rigorous testing processes well in
advance. Our Fedora Changes process facilitates the submission of
changesets long before the official release cycle begins. As part of
this effort, we're excited to introduce Rawhide Test Days, an
initiative designed to test these changesets thoroughly and identify
any potential (blocker) bugs early on.

To kick off this exciting journey, we're focusing our efforts on
testing DNF 5 – a crucial changeset proposed for Fedora Linux 41[0].
With the introduction of the brand new DNF5 package in Rawhide, we're
organizing a test days to gather initial feedback before it becomes
the default. We'll be rigorously testing DNF5 against its basic
acceptance criteria to ensure a seamless transition.

Mark your calendars for our Rawhide Test Days, taking place from
Friday, March 15th, through Tuesday, March 19th. Your participation
during this week will be invaluable as we work together to refine
Fedora Linux for its upcoming release.

Ready to dive in? Visit our test week page [1] to learn more about how
you can contribute and make your mark on the future of Fedora.

Happy testing, and we can't wait to see you there!

Best regards,
//sumantro

[0] https://fedoraproject.org/wiki/Changes/ReplaceDnfWithDnf5
[1] http://fedoraproject.org/wiki/Test_Day:2024-03-15_Fedora_40_DNF_5



-- 
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: dmesg suddenly fails when run as normal user on FC39

[Jeffrey Walton]

On Wed, Mar 13, 2024 at 7:05 PM Ron Flory via users
 wrote:
>
>  does not happen on FC38, or any prior RedHat/Fedora version since forever.
>
>dmesg
>dmesg: read kernel buffer failed: Operation not permitted
>
>  Userspace scripts (such as used to read pics from cameras & sdcards) and 
> many progs often use dmesg to detect or identify things like startup probe 
> info, USB devs, partition numbers etc.
>
>  I worked around this by setting the suid bit of `which dmesg`, but it would 
> be rude to force everybody to manually do this as part of post-install 
> cleanup.
>
>  Hopefully an unintended side-effect and not a new "feature" that wasn't 
> thought through completely.  A web-search suggests debian/ubuntu may have 
> been doing this for awhile- but we really don't need to be just like them...  
>   ;)

You can restore old behavior with the following.

# sysctl kernel.dmesg_restrict=0

Put in /etc/sysctl.d/10-dmesg.conf to make it permanent.

Jeff
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: dmesg suddenly fails when run as normal user on FC39

[Ron Flory via users]

On 3/13/2024 6:54 PM, Sam Varshavchik wrote:

Ron Flory via users writes:


»Hi-

 does not happen on FC38, or any prior RedHat/Fedora version since 
forever.


Sounds like this has landed:

https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/thread/U2XA6J5BGPKMS54YM7DTOI4QHUXQTARI 



 Thanks for the link.

 I can see both sides of it.  At the same time, I can neither 
fully condemn, nor enthusiastically support this.  Subtle side-effects 
with existing practices and applications will haunt us for a long time.


--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: dmesg suddenly fails when run as normal user on FC39

[Sam Varshavchik]

Ron Flory via users writes:


»Hi-

 does not happen on FC38, or any prior RedHat/Fedora version since forever.


Sounds like this has landed:

https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/thread/U2XA6J5BGPKMS54YM7DTOI4QHUXQTARI/




pgpHS0_YMt3pr.pgp
Description: PGP signature
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: dmesg suddenly fails when run as normal user on FC39

[Samuel Sieb]

On 3/13/24 16:05, Ron Flory via users wrote:
  does not happen on FC38, or any prior RedHat/Fedora version since 
forever.


    dmesg
    dmesg: read kernel buffer failed: Operation not permitted

  Userspace scripts (such as used to read pics from cameras & sdcards) 
and many progs often use dmesg to detect or identify things like startup 
probe info, USB devs, partition numbers etc.


  I worked around this by setting the suid bit of `which dmesg`, but it 
would be rude to force everybody to manually do this as part of 
post-install cleanup.


  Hopefully an unintended side-effect and not a new "feature" that 
wasn't thought through completely.  A web-search suggests debian/ubuntu 
may have been doing this for awhile- but we really don't need to be just 
like them...    ;)


This was intentional and there was a thread about this recently, 
probably on devel or test.  It's considered to be a big security issue.


If you're in the wheel group, you can use "journalctl -k".
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: dmesg suddenly fails when run as normal user on FC39

[Roger Wells]

same observation.
[]$ uname -r
6.7.7-200.fc39.x86_64

On 3/13/24 19:05, Ron Flory via users wrote:

Hi-

 does not happen on FC38, or any prior RedHat/Fedora version since 
forever.


   dmesg
   dmesg: read kernel buffer failed: Operation not permitted

 Userspace scripts (such as used to read pics from cameras & sdcards) 
and many progs often use dmesg to detect or identify things like 
startup probe info, USB devs, partition numbers etc.


 I worked around this by setting the suid bit of `which dmesg`, but it 
would be rude to force everybody to manually do this as part of 
post-install cleanup.


 Hopefully an unintended side-effect and not a new "feature" that 
wasn't thought through completely.  A web-search suggests 
debian/ubuntu may have been doing this for awhile- but we really don't 
need to be just like them...    ;)


--
___
users mailing list --users@lists.fedoraproject.org
To unsubscribe send an email tousers-le...@lists.fedoraproject.org
Fedora Code of 
Conduct:https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines
List 
Archives:https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report 
it:https://pagure.io/fedora-infrastructure/new_issue--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

dmesg suddenly fails when run as normal user on FC39

[Ron Flory via users]

Hi-

 does not happen on FC38, or any prior RedHat/Fedora version since 
forever.


   dmesg
   dmesg: read kernel buffer failed: Operation not permitted

 Userspace scripts (such as used to read pics from cameras & sdcards) 
and many progs often use dmesg to detect or identify things like startup 
probe info, USB devs, partition numbers etc.


 I worked around this by setting the suid bit of `which dmesg`, but it 
would be rude to force everybody to manually do this as part of 
post-install cleanup.


 Hopefully an unintended side-effect and not a new "feature" that 
wasn't thought through completely.  A web-search suggests debian/ubuntu 
may have been doing this for awhile- but we really don't need to be just 
like them...    ;)
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Failed to start jobs message from today's F39 update

[Barry]

> On 13 Mar 2024, at 17:12, Neal Becker  wrote:
> 
> I need to see the lines before this, and maybe after.  Any ideas?

Once I find a time of interest I have use the —since and - before to get a time 
bounded slice of logs.

Barry


--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Failed to start jobs message from today's F39 update

[Tim Evans]

On 3/13/24 14:42, Joe Zeff wrote:

On 03/13/2024 12:33 PM, Mike Wright wrote:
I couldn't find any way to pass grep options to -g but grep itself has 
-A and -B for showing "n" number of lines After or Before the matched 
context.


If you need to pass options to grep, consider piping the output of 
journalctl through grep instead.


Or pipe the output of journalctl to 'less' and use its built-in search 
functions.

--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Failed to start jobs message from today's F39 update

[Samuel Sieb]

On 3/13/24 10:10, Neal Becker wrote:



On Tue, Mar 12, 2024 at 2:50 PM Joe Zeff > wrote:


On 03/12/2024 12:33 PM, Neal Becker wrote:
 > Failed to start jobs: Failed to enqueue some jobs, see logs for
details:
 > Invalid argument
 >
 > Should I worry?  I don't even know what armadillo is.

Did you look at the logs and if not, why not?  Checking Wikipedia,
armadillo is a C++ library for linear algebra.


I didn't search, because I don't know an easy way to do it.  Back when 
syslog was text it was easy.

Let's try:
journalctl -g 'Failed to start jobs:'
...
Mar 13 07:17:37 nbecker0 packagekitd[723125]: Failed to start jobs: 
Failed to enqueue some jobs, see logs for details: Invalid argument


OK, that still tells me nothing.  I need to see the lines before this, 
and maybe after.  Any ideas?


It uses commands similar to less (maybe it's actually using less).  Run 
"journalctl -b".  Press the "/" key and type the text you want to find. 
Then you can see the context and use back and forward keys to move around.


You can also run "journalctl -u packagekit", although my logs show a 
different label for packagekit than what you have there.


Mar 12 14:04:07 fedora PackageKit[4010770]: get-updates transaction 
/20675_bedceece from uid 1000 finished with success after 2730ms

--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Failed to start jobs message from today's F39 update

[Joe Zeff]

On 03/13/2024 12:33 PM, Mike Wright wrote:
I couldn't find any way to pass grep options to -g but grep itself has 
-A and -B for showing "n" number of lines After or Before the matched 
context.


If you need to pass options to grep, consider piping the output of 
journalctl through grep instead.

--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Failed to start jobs message from today's F39 update

[Mike Wright]

On 3/13/24 10:10, Neal Becker wrote:

On Tue, Mar 12, 2024 at 2:50 PM Joe Zeff  wrote:


On 03/12/2024 12:33 PM, Neal Becker wrote:

Failed to start jobs: Failed to enqueue some jobs, see logs for details:
Invalid argument

Should I worry?  I don't even know what armadillo is.


Did you look at the logs and if not, why not?  Checking Wikipedia,
armadillo is a C++ library for linear algebra.



I didn't search, because I don't know an easy way to do it.  Back when
syslog was text it was easy.
Let's try:
journalctl -g 'Failed to start jobs:'


-g --grep

I couldn't find any way to pass grep options to -g but grep itself has 
-A and -B for showing "n" number of lines After or Before the matched 
context.


The journalctl manpage has an option -n --lines that combined with -g 
MAY do something like that but I haven't tried it yet.



...
Mar 13 07:17:37 nbecker0 packagekitd[723125]: Failed to start jobs: Failed
to enqueue some jobs, see logs for details: Invalid argument

OK, that still tells me nothing.  I need to see the lines before this, and
maybe after.  Any ideas?


--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Failed to start jobs message from today's F39 update

[Neal Becker]

On Tue, Mar 12, 2024 at 2:50 PM Joe Zeff  wrote:

> On 03/12/2024 12:33 PM, Neal Becker wrote:
> > Failed to start jobs: Failed to enqueue some jobs, see logs for details:
> > Invalid argument
> >
> > Should I worry?  I don't even know what armadillo is.
>
> Did you look at the logs and if not, why not?  Checking Wikipedia,
> armadillo is a C++ library for linear algebra.
>

I didn't search, because I don't know an easy way to do it.  Back when
syslog was text it was easy.
Let's try:
journalctl -g 'Failed to start jobs:'
...
Mar 13 07:17:37 nbecker0 packagekitd[723125]: Failed to start jobs: Failed
to enqueue some jobs, see logs for details: Invalid argument

OK, that still tells me nothing.  I need to see the lines before this, and
maybe after.  Any ideas?
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Configuring LXC containers

[Mike Wright]

On 3/13/24 04:45, Patrick O'Callaghan wrote:

On Tue, 2024-03-12 at 15:36 -0700, Mike Wright wrote:

On 3/11/24 14:41, Patrick O'Callaghan wrote:

On Sun, 2024-03-10 at 16:39 +, Patrick O'Callaghan wrote:

I'd like to play with LXC but I find the docs not very newbie-
friendly.
I'm trying to follow a guide at:

https://brandonrozek.com/blog/lxc-fedora-38/

(basically because it mentions Fedora). I followed the steps
closely
and rebooted, but I get the following error:

     $ systemd-run --unit=my-unit --user --scope -p "Delegate=yes"
--
lxc-start test
     Running scope as unit: my-unit.scope
     lxc-start: test: lxccontainer.c: wait_on_daemonized_start:
877
Received container state "ABORTING" instead of "RUNNING"
     lxc-start: test: tools/lxc_start.c: main: 306 The container
failed
to start
     lxc-start: test: tools/lxc_start.c: main: 309 To get more
details,
run the container in foreground mode
     lxc-start: test: tools/lxc_start.c: main: 311 Additional
information can be obtained by setting the --logfile and --
logpriority options
 
Any insights would be welcome. (Just in case, I tried running

with
SElinux turned off, but it made no difference.)


One thing: on running lxc-checkconfig I get:
...
Cgroup v1 systemd controller: missing
Cgroup v1 freezer controller: missing
Cgroup ns_cgroup: required

...

(everything else is OK).


The first two are irrelevant.  It uses cgroup2 now.  3rd one I don't
understand.

How is your test container working?


It isn't. I still get the same errors on startup.


I've been playing along over here and now have a container that
reports
"UNPRIVILEGED true" using lxc-ls -f.  It starts and runs but is
unusable.  lxc-start -n C1 -F shows the bootup sequence and it is
full
of [FAILED] sections.  root can't even change to /root: permission
denied.  Almost everything is owned by 65534:65534.  If I manually
set
an IP and default route I have networking and it uses my DNS
container
successfully.

I found this: https://brandonrozek.com/blog/lxc-fedora-38/ "Setting
up
unprivileged containers with LXC on Fedora 38" and how to use systemd
to
start and stop the containers.  It works but doesn't solve the other
problems I'm seeing.


Yes, I'd found that page a couple of days ago and tried following it.
Same problems as before.

I'm thinking this isn't worth the hassle. 


I reached the same conclusion wrt unprivileged containers.  Nonetheless, 
I'm still very happy using privileged containers.  They're up in a 
second, none have ever crashed or become unstable.  I find them ideal 
for isolating individual services on my network and for conducting quick 
experiments.



My main interest in lxc was
to run a small containerised VPN, but Fedora seems to have much better
support for docker (via podman) so I'll probably concentrate on that.


Good luck!
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Configuring LXC containers

[Patrick O'Callaghan]

On Tue, 2024-03-12 at 15:36 -0700, Mike Wright wrote:
> On 3/11/24 14:41, Patrick O'Callaghan wrote:
> > On Sun, 2024-03-10 at 16:39 +, Patrick O'Callaghan wrote:
> > > I'd like to play with LXC but I find the docs not very newbie-
> > > friendly.
> > > I'm trying to follow a guide at:
> > > 
> > > https://brandonrozek.com/blog/lxc-fedora-38/
> > > 
> > > (basically because it mentions Fedora). I followed the steps
> > > closely
> > > and rebooted, but I get the following error:
> > > 
> > >     $ systemd-run --unit=my-unit --user --scope -p "Delegate=yes"
> > > --
> > > lxc-start test
> > >     Running scope as unit: my-unit.scope
> > >     lxc-start: test: lxccontainer.c: wait_on_daemonized_start:
> > > 877
> > > Received container state "ABORTING" instead of "RUNNING"
> > >     lxc-start: test: tools/lxc_start.c: main: 306 The container
> > > failed
> > > to start
> > >     lxc-start: test: tools/lxc_start.c: main: 309 To get more
> > > details,
> > > run the container in foreground mode
> > >     lxc-start: test: tools/lxc_start.c: main: 311 Additional
> > > information can be obtained by setting the --logfile and --
> > > logpriority options
> > >     
> > > Any insights would be welcome. (Just in case, I tried running
> > > with
> > > SElinux turned off, but it made no difference.)
> > 
> > One thing: on running lxc-checkconfig I get:
> > ...
> > Cgroup v1 systemd controller: missing
> > Cgroup v1 freezer controller: missing
> > Cgroup ns_cgroup: required
> > 
> > ...
> > 
> > (everything else is OK).
> 
> The first two are irrelevant.  It uses cgroup2 now.  3rd one I don't 
> understand.
> 
> How is your test container working?
> 
It isn't. I still get the same errors on startup.

> I've been playing along over here and now have a container that
> reports 
> "UNPRIVILEGED true" using lxc-ls -f.  It starts and runs but is 
> unusable.  lxc-start -n C1 -F shows the bootup sequence and it is
> full 
> of [FAILED] sections.  root can't even change to /root: permission 
> denied.  Almost everything is owned by 65534:65534.  If I manually
> set 
> an IP and default route I have networking and it uses my DNS
> container 
> successfully.
> 
> I found this: https://brandonrozek.com/blog/lxc-fedora-38/ "Setting
> up 
> unprivileged containers with LXC on Fedora 38" and how to use systemd
> to 
> start and stop the containers.  It works but doesn't solve the other 
> problems I'm seeing.

Yes, I'd found that page a couple of days ago and tried following it.
Same problems as before.

I'm thinking this isn't worth the hassle. My main interest in lxc was
to run a small containerised VPN, but Fedora seems to have much better
support for docker (via podman) so I'll probably concentrate on that.

poc
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue