Re: Firmware packages

[Aleksei Bavshin]

On 11/8/21 22:36, Miroslav Suchý wrote:
In the recent discussion about saving space (in the ELF thread) there 
poped up linux-firmware topic several time. Let's kick it off as 
separate thread.


I have several question and I am unable to find the answer for them.

1. How do I find which firmware package I need? On my workstation I have:

$ rpm-qa|grepfirmware |wc-l
27

I seriously doubt I need all of them. I definitely do not need them on 
server, where I never add any new HW. But how do I know which one is in 
use and which not?


From my (fairly limited) knowledge, you'll have to look at `modinfo` 
for loaded modules or `MODULE_FIRMWARE` and `request_firmware.*` API 
usage within the kernel sources. I'm not aware if that documents all the 
firmware files in use, but hopefully someone from kernel or 
linux-firmware maintenance teams can chime in.


AFAIK, there is no information about the mapping of device ids -> fw 
files available. I.e., let's say, `iwlwifi` in 5.15.0 declares 47 unique 
firmware files and 77 supported PCI ids. But each of those PCI ids would 
require only a small subset of these 47 firmware binaries. Thus, the 
`iwl.*-firmware` packages can be split in a way it is done right now and 
installed/removed as necessary.


It should possible to collect the data from the kernel source manually, 
but imagine the effort to do that and to keep it up-to-date...


---
I considered proposing to use rpm metadata for the very same purpose, 
something like


Supplements: device(pci:8086:a0f0) >= rev20
Supplements: device(usb:8087:0026)

or
Provides: firmware(pci:8086:a0f0)
Provides: firmware(usb:8087:0026)

but we'd really want to have that autogenerated, and there's no input 
data readily available for that.
Also, you'd want to expose the hardware information from the rpm side as 
well, which is a whole another problem. I believe we still can't get CPU 
hwcaps exposed, and this would add lspci/lsusb information to the mix.



2. How the firmware packages actually work? Do I need them to be present 
every time? Or when module is loaded? Or something else? (sorry if this 
too naive question).


A module can load a firmware binary with the `request_firmware` API at 
any moment of it's lifetime. Usually, this happens when the module is 
initialized or discovers a new supported device, but I don't believe 
that is a strictly enforced rule.


The process itself is complicated enough (I recall it used to involve 
udev as an intermediary to access the filesystem), and may have a place 
for on-demand firmware package installation. But that's prone to breaks 
and won't function offline. Also, see above for required device id -> 
firmware files mapping.


3. The linux-firmare has 100MB. And cca 280 MB extracted. Is it about 
the time to split the package? Here are the biggest space eater of the 
space:


18M /usr/lib/firmware/amdgpu
18M /usr/lib/firmware/qcom
28M /usr/lib/firmware/intel
31M /usr/lib/firmware/mrvl
47M /usr/lib/firmware/mellanox


You can slightly reduce the installation footprint if you have 
minimum/maximum supported kernel version. Some of the firmware binaries 
have an API version, and the kernel will use only currently supported 
API (I'll point to `iwlwifi` as an example again. It's what lead me to a 
rabbit hole of firmware loaders, after all). The rest are kept there 
only to support older kernels. But that doesn't apply to all the 
firmware files and drivers, and again, the compat database has to be 
collected and updated manually.



Miroslav

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure



--
Best regards,
Aleksei Bavshin


OpenPGP_signature
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Fedora-Cloud-35-20211109.0 compose check report

[Fedora compose checker]

No missing expected images.

Failed openQA tests: 1/8 (aarch64)

New failures (same test not failed in Fedora-Cloud-35-20211108.0):

ID: 1057790 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi
URL: https://openqa.fedoraproject.org/tests/1057790

Soft failed openQA tests: 1/8 (x86_64)
(Tests completed, but using a workaround for a known bug)

Old soft failures (same test soft failed in Fedora-Cloud-35-20211108.0):

ID: 1057783 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://openqa.fedoraproject.org/tests/1057783

Passed openQA tests: 7/8 (x86_64), 7/8 (aarch64)
-- 
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Fedora 35 - gedit

[Michael J. Baars]

Hi All,

I've been working with Fedora for years now, and I just installed the newest 
Fedora Workstation 35 on one of my computers.

Since I use gedit a lot for editing source codes, gedit was one of the first 
programs I tried to launch. Now, there I get into trouble. After opening a few
source files and trying to start off where I left, I noticed that the mouse 
pointer (and the line number) often does not end up where I clicked the mouse 
when
trying to position the cursor (for cutting and pasting for example). This is 
the very first time that I experience this problem.

Help would be appreciated,

Best regards,
Mischa Baars.

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Long-running side tag for porting Fedora to C99 (no implicit decls)

[Vít Ondruch]

Dne 08. 11. 21 v 21:39 Kevin Fenzi napsal(a):

On Mon, Nov 08, 2021 at 02:06:43PM +0100, Florian Weimer wrote:

I would like to create a long-running rawhide side tag for preparing
Fedora for the removal of implicit function declarations from the GCC
defaults.  This is a change that happened in the C99 version of the
language, but GCC could not adopt at the time because too much software
was broken by it.  Even today, there are build failures, and, arguably
worse, successful builds with different feature sets.

The goal is to disable implicit function declarations in GCC 13, to be
released in spring 2023 (not next year's GCC 12 version).  This plan was
presented at this year's Cauldron, and was met with approval:

   Eliminating implicit function declarations
   

I have some space to work on this during the coming months, for
implementing the buildroot changes (in gcc and presumably
redhat-rpm-config, built off branches in dist-git), for creating some
HTML reports, and even for creating the package changes themselves.
Changes will be submitted to upstream projects initially.  Eventually,
we'll have to fix the Fedora packages if there's no upstream release
with the fixes.  We'll need some way to coordinate the fixes between
multiple developers, a way to find unapplied upstream fixes once we are
heading towards Fedora 38, and ideally some way to share patches across
distributions if the upstream project no longer exists/accepts patches.

If Fedora wants to support this, I'd need a long-running side tag in
Koji, and a few dist-git branches (for gcc and redhat-rpm-config).  I
can do the test builds as scratch builds, to conserve storage space and
not to pollute Koji with uninteresting NVRs.

Thoughts?

Isn't this an ideal use case for copr?



+1

Or maybe I just don't understand how the side-tag is going to be used. 
Will there be some modifications necessary for some packages (except 
those already listed)? Will these changes be compatible with rawhide? 
Will the side-tag ever be merged back into Rawhide?



Vít



Or is the lack of s390x (and non emulated armv7) there too much of a hurdle?

kevin

___
devel mailing list --devel@lists.fedoraproject.org
To unsubscribe send an email todevel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report 
it:https://pagure.io/fedora-infrastructure


OpenPGP_signature
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: F36 Change: Package information on ELF objects (System-Wide Change proposal)

[Vitaly Zaitsev via devel]

On 08/11/2021 22:24, Lennart Poettering wrote:

And I think that's a*good*  thing: JSON might not be perfect — because
nothing is —, but it's certainly one of the better designed generic
data formats around, and it's complexity is absolutely managable.


What about YAML?

--
Sincerely,
  Vitaly Zaitsev (vit...@easycoding.org)
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Self Introduction: Alexander Bulimov

[Vitaly Zaitsev via devel]

On 08/11/2021 17:19, Alexander Bulimov wrote:
The plan is to maintain it with Davide's help, and provide regular 
updates as the Time Appliance project is in the very active phase now.


Hello and welcome to Fedora.

Please follow this instructions:
https://docs.fedoraproject.org/en-US/package-maintainers/How_to_Get_Sponsored_into_the_Packager_Group/

--
Sincerely,
  Vitaly Zaitsev (vit...@easycoding.org)
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Package FFMPEG with royalty free codes (AV1, THEORA, VPX, OGG, OPUS, SPEEX, ...) for Fedora

[Vitaly Zaitsev via devel]

On 08/11/2021 16:47, Andreas Schneider wrote:

I have electron building offline for Fedora, you can find it here:
https://build.opensuse.org/package/show/network:im:signal/nodejs-electron


Electron core packaging is a quite trivial task (Arch Linux and Debian 
have already done this), but what about Electron applications (VS Code 
for example)?


Most of them download tons of bundled JS blobs from npm during the 
build. I don't think it will be easy (or even possible) to build 
everything from sources.


--
Sincerely,
  Vitaly Zaitsev (vit...@easycoding.org)
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: F36 Change: Package information on ELF objects (System-Wide Change proposal)

[Vít Ondruch]

Dne 09. 11. 21 v 10:14 Vitaly Zaitsev via devel napsal(a):

On 08/11/2021 22:24, Lennart Poettering wrote:

And I think that's a*good*  thing: JSON might not be perfect — because
nothing is —, but it's certainly one of the better designed generic
data formats around, and it's complexity is absolutely managable.


What about YAML?



JSON is (subset of) YAML

https://yaml.org/spec/1.2.2/#12-yaml-history



Vít



OpenPGP_signature
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: deltarpm usefulness?

[Rajeesh K V]

> > I remember seeing 60-70% reduction really often, and 90+ periodically.  I've
> > read Kevin's explanation of why it's not working as well now, but I wonder
> > what changed between the early implementation when results were very good
> > and now, when they really aren't.
>
> I think it's because you only see deltas from N to N+1 now and before
> you saw deltas from N to N+X before. So, I think if we made it somehow
> create older deltas, you would again see better savings. The issue
> doesn't just cause there to be fewer deltas, but it also causes those
> few be be against very recent changes, so less effective.

Would it make sense (and possible to implement fairly easily) to
generate deltas weekly instead of daily? That may already be a good
start; as I’d imagine bandwidth constrained users would generally try
to update on a weekly or monthly basis.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Long-running side tag for porting Fedora to C99 (no implicit decls)

[Florian Weimer]

* Kevin Fenzi:

> Isn't this an ideal use case for copr?

I don't know.  I could piece together the Koji API fairly easily, and
had hoped to reuse some of the script logic.

Or does COPR have direct support this?  Can I tell it directly to report
rawhide in a special buildroot?  Is there a programmatic way to access
the resulting log files?

(I won't need the built RPMs, which is why I would use scratch builds in
Koji.)

> Or is the lack of s390x (and non emulated armv7) there too much of a hurdle?

I would prefer to test on the real thing, true.

Thanks,
Florian
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Long-running side tag for porting Fedora to C99 (no implicit decls)

[Florian Weimer]

* Vít Ondruch:

> Or maybe I just don't understand how the side-tag is going to be
> used. Will there be some modifications necessary for some packages
> (except those already listed)?

The modifications can go directly into rawhide because they are
compatible with older compilers.  But at least in the beginning, I plan
to submit them just to upstream, hoping that the Fedora package gets
rebase to an upstream release with the fix before the switch to GCC 13.

> Will these changes be compatible with rawhide? Will the side-tag ever
> be merged back into Rawhide?

The side tag will not be merged back.

Thanks,
Florian
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Fedora-Cloud-34-20211109.0 compose check report

[Fedora compose checker]

No missing expected images.

Soft failed openQA tests: 1/8 (x86_64), 1/8 (aarch64)
(Tests completed, but using a workaround for a known bug)

Old soft failures (same test soft failed in Fedora-Cloud-34-20211108.0):

ID: 1057799 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://openqa.fedoraproject.org/tests/1057799
ID: 1057806 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi
URL: https://openqa.fedoraproject.org/tests/1057806

Passed openQA tests: 7/8 (x86_64), 7/8 (aarch64)
-- 
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: F36 Change: Package information on ELF objects (System-Wide Change proposal)

[Tomasz Torcz]

On Tue, Nov 09, 2021 at 10:14:25AM +0100, Vitaly Zaitsev via devel wrote:
> On 08/11/2021 22:24, Lennart Poettering wrote:
> > And I think that's a*good*  thing: JSON might not be perfect — because
> > nothing is —, but it's certainly one of the better designed generic
> > data formats around, and it's complexity is absolutely managable.
> 
> What about YAML?

  YAML is much more complicated that JSON. To the point that JSON
document is a valid YAML document.
  YAML spec (https://yaml.org/spec/1.2.2/) is about 66 pages when printed.

-- 
Tomasz TorczOnce you've read the dictionary,
@ttorcz:pipebreaker.pl  every other book is just a remix.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Fedora 36] Call for Test Days

[Sumantro Mukherjee]

Hi Fedora users, developers, and friends!

It's time to start thinking about Test Days for Fedora 36.

For anyone who isn't aware, a Test Day is an event usually focused
around IRC for interaction and a Wiki page for instructions and results,
with the aim being to get a bunch of interested users and developers
together to test a specific feature or area of the distribution. You can
run a Test Day on just about anything for which it would be useful to do
some fairly focused testing in 'real time' with a group of testers; it
doesn't have to be code, for instance, we often run Test Days for
l10n/i18n topics. For more information on Test Days, see
https://fedoraproject.org/wiki/QA/Test_Days .

Anyone who wants to can host their own Test Day, or you can request that
the QA group helps you out with organization or any combination of the
two. To propose a Test Day, just file a ticket in fedora-qa pagure - here's
an example https://pagure.io/fedora-qa/issue/624 . For
instructions on hosting a Test Day, see
https://fedoraproject.org/wiki/QA/SOP_Test_Day_management .

You can see the schedule at https://pagure.io/fedora-qa/issues?tags=test+days .
There are many slots open right now. Consider the development
schedule, though, in deciding when you want to run your Test Day - for
some topics you may want to avoid
the time before the Beta release or the time after the feature freeze
or the Final Freeze.

We normally aim to schedule Test Days on Thursdays; however, if you want
to run a series of related Test Days, it's often a good idea to do
something like Tuesday / Wednesday / Thursday of the same week (this is
how we usually run the X Test Week, for instance). If all the Thursday
slots fill up but more people want to run Test Days, we will open up
Tuesday slots as overflows. And finally, if you really want to run a
Test Day in a specific time frame due to the development schedule, but
the Thursday slot for that week is full, we can add a slot on another
day. We're flexible! Just put in your ticket the date or time frame you'd
like, and we'll figure it out from there.

If you don't want to run your own Test Day, but you are willing to
help with another, feel free to join one or more of already accepted
Test Days:

GNOME Test Day*
i18n Test Day*
Kernel Test Week(s)*
Upgrade Test Day*
IoT Test Week*
Cloud Test Day*
Fedora CoreOS Test Week*

And don't be afraid, there are a lot of more slots available for your
own Test Day!

[*] These are the test days we run generally to make sure everything
is working fine, the dates get announced as we move into the release
cycle.

If you have any questions about the Test Day process, please don't
hesitate to contact me or any member of the Fedora QA team on test at
lists.fedoraproject.org or in #fedora-qa on IRC. Thanks!

-- 
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Fedora 35 - gedit

[Mikel Olasagasti]

Hi Mischa,

Hau idatzi du Michael J. Baars (mjbaars1977.fedora.de...@gmail.com)
erabiltzaileak (2021 aza. 9, ar. (10:14)):
>
> Hi All,
>
> I've been working with Fedora for years now, and I just installed the newest 
> Fedora Workstation 35 on one of my computers.
>
> Since I use gedit a lot for editing source codes, gedit was one of the first 
> programs I tried to launch. Now, there I get into trouble. After opening a few
> source files and trying to start off where I left, I noticed that the mouse 
> pointer (and the line number) often does not end up where I clicked the mouse 
> when
> trying to position the cursor (for cutting and pasting for example). This is 
> the very first time that I experience this problem.

This happened to me also with Fedora 34. I switched to
gnome-text-editor's flatpak as gedit replacement and, although is not
a complete replacement, it has some nice features.

Kind regards,
Mikel
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Fedora 35 - gedit

[Michael J. Baars]

Hi Mikel,

Good to know! I would otherwise have downgraded to Fedora 34. Now I don't
have to find out for myself the hard way that that wouldn't have been very
much of a solution.

I will try one of the Gnome mailing lists as well, see if we can find some
people that are able to fix this.

Best regards,
Mischa.

On Tue, 9 Nov 2021, 12:08 Mikel Olasagasti,  wrote:

> Hi Mischa,
>
> Hau idatzi du Michael J. Baars (mjbaars1977.fedora.de...@gmail.com)
> erabiltzaileak (2021 aza. 9, ar. (10:14)):
> >
> > Hi All,
> >
> > I've been working with Fedora for years now, and I just installed the
> newest Fedora Workstation 35 on one of my computers.
> >
> > Since I use gedit a lot for editing source codes, gedit was one of the
> first programs I tried to launch. Now, there I get into trouble. After
> opening a few
> > source files and trying to start off where I left, I noticed that the
> mouse pointer (and the line number) often does not end up where I clicked
> the mouse when
> > trying to position the cursor (for cutting and pasting for example).
> This is the very first time that I experience this problem.
>
> This happened to me also with Fedora 34. I switched to
> gnome-text-editor's flatpak as gedit replacement and, although is not
> a complete replacement, it has some nice features.
>
> Kind regards,
> Mikel
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Fedora 35 - gedit

[Fabio Valentini]

On Tue, Nov 9, 2021 at 10:13 AM Michael J. Baars
 wrote:
>
> Hi All,
>
> I've been working with Fedora for years now, and I just installed the newest 
> Fedora Workstation 35 on one of my computers.
>
> Since I use gedit a lot for editing source codes, gedit was one of the first 
> programs I tried to launch. Now, there I get into trouble. After opening a few
> source files and trying to start off where I left, I noticed that the mouse 
> pointer (and the line number) often does not end up where I clicked the mouse 
> when
> trying to position the cursor (for cutting and pasting for example). This is 
> the very first time that I experience this problem.
>
> Help would be appreciated,

Have you tried just updating your Fedora 35 system with the most recent updates?
Because I noticed a recent gnome-shell and mutter update that claims
to fix jumping cursor positions in text editors:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-4ce970eca6

Fabio
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

something weird with python3 on rawhide builds? I'm stumped

[Kaleb Keithley]

I'm trying to do a scratch build but not getting python3-devel installed.

The .spec file has BR: python3-devel, and rpm -qp --requires on the
.src.rpm shows it has the needed Requires: python3-devel.

E.g. https://kojipkgs.fedoraproject.org//work/tasks/6036/78546036/root.log

Regular builds of the package found python3-devel the last time I built.

-- 

Kaleb
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: something weird with python3 on rawhide builds? I'm stumped

[Mamoru TASAKA]

Kaleb Keithley wrote on 2021/11/09 21:14:

I'm trying to do a scratch build but not getting python3-devel installed.

The .spec file has BR: python3-devel, and rpm -qp --requires on the
.src.rpm shows it has the needed Requires: python3-devel.

E.g. https://kojipkgs.fedoraproject.org//work/tasks/6036/78546036/root.log

Regular builds of the package found python3-devel the last time I built.




But the above root.log actually shows:


 python3-devel  x86_64  3.10.0-2.fc36 build  206 k


A possible case is that configuration script cannot find python 3."10" .

Regards,
Mamoru
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Fedora 35 - gedit

[Michael J. Baars]

On Tue, 2021-11-09 at 13:00 +0100, Fabio Valentini wrote:
> On Tue, Nov 9, 2021 at 10:13 AM Michael J. Baars
>  wrote:
> > Hi All,
> > 
> > I've been working with Fedora for years now, and I just installed the 
> > newest Fedora Workstation 35 on one of my computers.
> > 
> > Since I use gedit a lot for editing source codes, gedit was one of the 
> > first programs I tried to launch. Now, there I get into trouble. After 
> > opening a few
> > source files and trying to start off where I left, I noticed that the mouse 
> > pointer (and the line number) often does not end up where I clicked the 
> > mouse
> > when
> > trying to position the cursor (for cutting and pasting for example). This 
> > is the very first time that I experience this problem.
> > 
> > Help would be appreciated,
> 
> Have you tried just updating your Fedora 35 system with the most recent 
> updates?
> Because I noticed a recent gnome-shell and mutter update that claims
> to fix jumping cursor positions in text editors:
> https://bodhi.fedoraproject.org/updates/FEDORA-2021-4ce970eca6
> 
> Fabio

Hi,

No, not yet. I will in just a minute if you say that should help. Let me get 
back on this. By the way, it's not like the window is scrolling into position, 
it's
the cursor and the mouse pointer that end up on the wrong line number. Let me 
try to update ...

I did write an email to the gnome applications (discourse) mailing list. Hope 
that will help too.

Mischa.

> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it: 
> https://pagure.io/fedora-infrastructure
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Fedora rawhide compose report: 20211109.n.0 changes

[Fedora Rawhide Report]

OLD: Fedora-Rawhide-20211108.n.0
NEW: Fedora-Rawhide-20211109.n.0

= SUMMARY =
Added images:0
Dropped images:  1
Added packages:  4
Dropped packages:5
Upgraded packages:   90
Downgraded packages: 0

Size of added packages:  123.44 KiB
Size of dropped packages:5.86 MiB
Size of upgraded packages:   1.77 GiB
Size of downgraded packages: 0 B

Size change of upgraded packages:   3.51 MiB
Size change of downgraded packages: 0 B

= ADDED IMAGES =

= DROPPED IMAGES =
Image: Silverblue dvd-ostree x86_64
Path: 
Silverblue/x86_64/iso/Fedora-Silverblue-ostree-x86_64-Rawhide-20211108.n.0.iso

= ADDED PACKAGES =
Package: python-azure-mgmt-servicelinker-1.0.0b1-2.fc36
Summary: Microsoft Azure Servicelinker Management Client Library for Python
RPMs:python3-azure-mgmt-servicelinker
Size:45.99 KiB

Package: python-cro-0.0.5.0-1.fc36
Summary: An implementation of CRO metaheuristic algorithm
RPMs:python3-cro
Size:28.83 KiB

Package: rust-dirs3-3.0.2-1.fc36
Summary: Platform abstractions for common directories
RPMs:rust-dirs3+default-devel rust-dirs3-devel
Size:27.42 KiB

Package: rust-open1-1.7.1-1.fc36
Summary: Open a path or URL using the program configured on the system
RPMs:rust-open1+default-devel rust-open1-devel
Size:21.20 KiB


= DROPPED PACKAGES =
Package: kdocker-5.3-4.fc35
Summary: Dock any application in the system tray
RPMs:kdocker
Size:699.88 KiB

Package: perl-Nagios-Plugin-0.37-21.fc35
Summary: Family of perl modules to streamline writing Nagios plugins
RPMs:perl-Nagios-Plugin
Size:26.70 KiB

Package: python-email_reply_parser-0.3.0-20140523git76e9481.fc35.24
Summary: Email reply parser library for Python 2
RPMs:python3-email_reply_parser
Size:15.52 KiB

Package: python-power-1.4-24.fc35
Summary: Cross-platform system power status information
RPMs:python3-power
Size:28.30 KiB

Package: yarock-1.4.0-13.fc35
Summary: Lightweight, beautiful music player
RPMs:yarock
Size:5.11 MiB


= UPGRADED PACKAGES =
Package:  NetworkManager-strongswan-1.5.2-1.fc36
Old package:  NetworkManager-strongswan-1.5.0-4.fc35
Summary:  NetworkManager strongSwan IPSec VPN plug-in
RPMs: NetworkManager-strongswan NetworkManager-strongswan-gnome
Size: 203.80 KiB
Size change:  437 B
Changelog:
  * Mon Nov 08 2021 Petr Menk  - 1.5.2-1
  - Update to 1.5.2


Package:  apache-commons-pool-1.6-27.fc36
Old package:  apache-commons-pool-1.6-26.fc35
Summary:  Apache Commons Pool Package
RPMs: apache-commons-pool apache-commons-pool-javadoc
Size: 491.56 KiB
Size change:  -41 B
Changelog:
  * Mon Nov 08 2021 Christian Schuermann  1.6-27
  - Cleanup spec file
  - Enable tests


Package:  awscli-1.22.0-1.fc36
Old package:  awscli-1.21.12-1.fc36
Summary:  Universal Command Line Environment for AWS
RPMs: awscli
Size: 2.13 MiB
Size change:  22.18 KiB
Changelog:
  * Mon Nov 08 2021 Gwyn Ciesla  - 1.22.0-1
  - 1.22.0


Package:  catatonit-0.1.7-1.fc36
Old package:  catatonit-0.1.6-1.fc36
Summary:  A signal-forwarding process manager for containers
RPMs: catatonit
Size: 1.42 MiB
Size change:  12.49 KiB
Changelog:
  * Mon Nov 01 2021 RH Container Bot  - 
0.1.7-1
  - autobuilt v0.1.7


Package:  containers-common-4:1-35.fc36
Old package:  containers-common-4:1-34.fc36
Summary:  Common configuration and documentation for containers
RPMs: containers-common
Size: 73.15 KiB
Size change:  318 B
Changelog:
  * Mon Nov 08 2021 Dan Walsh  - 4:1-35
  - Update to grab latest man pages and configuration files


Package:  dialog-1.3-38.20211107.fc36
Old package:  dialog-1.3-37.20210621.fc35
Summary:  A utility for creating TTY dialog boxes
RPMs: dialog dialog-devel
Size: 1.71 MiB
Size change:  -2.09 KiB
Changelog:
  * Mon Nov 08 2021 Miroslav Lichvar  - 1.3-38.20211107
  - update to 1.3-20211107


Package:  dkms-3.0.0-1.fc36
Old package:  dkms-2.8.8-1.fc36
Summary:  Dynamic Kernel Module Support Framework
RPMs: dkms
Size: 57.56 KiB
Size change:  -422 B
Changelog:
  * Mon Nov 08 2021 Simone Caronni  - 3.0.0-1
  - Update to 3.0.0.


Package:  dummy-test-package-gloster-0-5716.fc36
Old package:  dummy-test-package-gloster-0-5696.fc36
Summary:  Dummy Test Package called Gloster
RPMs: dummy-test-package-gloster
Size: 349.47 KiB
Size change:  1.24 KiB
Changelog:
  * Mon Nov 08 2021 packagerbot  - 0-5697
  - rebuilt

  * Mon Nov 08 2021 packagerbot  - 0-5698
  - rebuilt

  * Mon Nov 08 2021 packagerbot  - 0-5699
  - rebuilt

  * Mon Nov 08 2021 packagerbot  - 0-5700
  - rebuilt

  * Mon Nov 08 2021 packagerbot  - 0-5701
  - rebuilt

  * Mon Nov 08 2021 packagerbot  - 0-5702
  - rebuilt

  * Mon Nov 08 2021 packagerbot  - 0-5703
  - rebuilt

  * Mon Nov 08 2021 packagerbot  - 0-5704
  - rebuilt

  * Mon Nov 08 2021 packagerbot  - 0-5705

Re: something weird with python3 on rawhide builds? I'm stumped

[Kaleb Keithley]

On Tue, Nov 9, 2021 at 7:22 AM Mamoru TASAKA 
wrote:

> Kaleb Keithley wrote on 2021/11/09 21:14:
> > I'm trying to do a scratch build but not getting python3-devel installed.
> >
> > The .spec file has BR: python3-devel, and rpm -qp --requires on the
> > .src.rpm shows it has the needed Requires: python3-devel.
> >
> > E.g.
> https://kojipkgs.fedoraproject.org//work/tasks/6036/78546036/root.log
> >
> > Regular builds of the package found python3-devel the last time I built.
> >
> >
>
> But the above root.log actually shows:
>
> >  python3-devel  x86_64  3.10.0-2.fc36 build  206 k
>
> A possible case is that configuration script cannot find python 3."10" .
>

gah... I swear I searched for that last night. It was very late.

Yes, you're probably correct about the config script. Thanks for looking.

-- 

Kaleb
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Fedora 35 - gedit

[Michael J. Baars]

On Tue, 2021-11-09 at 13:00 +0100, Fabio Valentini wrote:
> On Tue, Nov 9, 2021 at 10:13 AM Michael J. Baars
>  wrote:
> > Hi All,
> > 
> > I've been working with Fedora for years now, and I just installed the 
> > newest Fedora Workstation 35 on one of my computers.
> > 
> > Since I use gedit a lot for editing source codes, gedit was one of the 
> > first programs I tried to launch. Now, there I get into trouble. After 
> > opening a few
> > source files and trying to start off where I left, I noticed that the mouse 
> > pointer (and the line number) often does not end up where I clicked the 
> > mouse
> > when
> > trying to position the cursor (for cutting and pasting for example). This 
> > is the very first time that I experience this problem.
> > 
> > Help would be appreciated,
> 
> Have you tried just updating your Fedora 35 system with the most recent 
> updates?
> Because I noticed a recent gnome-shell and mutter update that claims
> to fix jumping cursor positions in text editors:
> https://bodhi.fedoraproject.org/updates/FEDORA-2021-4ce970eca6
> 

Ok, well, I don't know exactly when Fedora 35 was released, but neither 'dnf 
distro-sync' not 'dnf check-update' wants to install the desired update or 
anything
at all for that matter. November 2 :)

> Fabio
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it: 
> https://pagure.io/fedora-infrastructure
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: deltarpm usefulness?

[Stephen John Smoogen]

On Tue, 9 Nov 2021 at 04:39, Rajeesh K V  wrote:
>
> > > I remember seeing 60-70% reduction really often, and 90+ periodically.  
> > > I've
> > > read Kevin's explanation of why it's not working as well now, but I wonder
> > > what changed between the early implementation when results were very good
> > > and now, when they really aren't.
> >
> > I think it's because you only see deltas from N to N+1 now and before
> > you saw deltas from N to N+X before. So, I think if we made it somehow
> > create older deltas, you would again see better savings. The issue
> > doesn't just cause there to be fewer deltas, but it also causes those
> > few be be against very recent changes, so less effective.
>
> Would it make sense (and possible to implement fairly easily) to
> generate deltas weekly instead of daily? That may already be a good
> start; as I’d imagine bandwidth constrained users would generally try
> to update on a weekly or monthly basis.

Not easily for 2 reasons:

1. deltas are package to package and many packages rev 4-6 times a
week (I am looking at you, kernel). So a once a week delta update
would have to make deltas against each of those packages for both
people who are resource constrained and those who are not.
2. Each 'compose' of Fedora is like a manufacturing line where if you
turn off some part, the rest after that point break because something
they expect is not there. If we turn off deltas altogether, we can
clean up various bits that were expected afterwards but someone would
need to do that work while doing all the usual work.

So you would need to set up a seperate compose pipeline which would do
this once a week and put those in a tree which is distinct from the
regular daily Fedora. That requires doubling the number of servers and
increasing disk space. Both of which are limited resources on the part
of Fedora Infrastructure.


-- 
Stephen J Smoogen.
Let us be kind to one another, for most of us are fighting a hard
battle. -- Ian MacClaren
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Firmware packages

[Gary Buhrmaster]

On Tue, Nov 9, 2021 at 8:42 AM Aleksei Bavshin
 wrote:

> A module can load a firmware binary with the `request_firmware` API at
> any moment of it's lifetime. Usually, this happens when the module is
> initialized or discovers a new supported device, but I don't believe
> that is a strictly enforced rule.

And some drivers will check if the firmware is already
loaded and active on a device before loading (and
restarting it) again.

And some drivers will load regulatory specific firmware
for a device (meaning a fair percentage of the firmware
for the device which is shipped for the device may not
actually be used in one's location).
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

During the first update after installation: Failed to connect to bus: Invalid argument

[Peter Boy]

While updating right after installation of Fedora Server 35 today I get:

> [...]# sudo  dnf  update
>   ...
>   Cleanup  : glibc-langpack-de-2.34-7.fc35.x86_64   
> 303/306 
>   Cleanup  : glibc-gconv-extra-2.34-7.fc35.x86_64   
> 304/306 
>   Running Scriptlet: glibc-gconv-extra-2.34-7.fc35.x86_64   
> 304/306 
>   Cleanup  : glibc-common-2.34-7.fc35.x86_64
> 305/306 
>   Cleanup  : tzdata-2021b-1.fc35.noarch 
> 306/306 
>   Running Scriptlet: grub2-common-1:2.06-8.fc35.noarch  
> 306/306 
>   Running Scriptlet: selinux-policy-targeted-35.5-1.fc35.noarch 
> 306/306 
>   Running Scriptlet: clevis-18-4.fc35.x86_64
> 306/306 
>   Running Scriptlet: libwbclient-2:4.15.1-0.fc35.x86_64 
> 306/306 
>   Running Scriptlet: kernel-core-5.14.16-301.fc35.x86_64
> 306/306 
>   Running Scriptlet: sssd-common-2.6.0-2.fc35.x86_64
> 306/306 
>   Running Scriptlet: tzdata-2021b-1.fc35.noarch 
> 306/306 
> Failed to connect to bus: Invalid argument
> 
> Failed to connect to bus: Invalid argument
> 
> Failed to connect to bus: Invalid argument
> Failed to connect to bus: Invalid argument
> 
>   Verifying: clevis-pin-tpm2-0.3.0-2.fc35.x86_64  
> 1/306 
>   Verifying: freetype-2.11.0-1.fc35.x86_64
> 2/306 


I first suspected there was an error during installation and repeated it, 
watching for error / warning messages (none). The error messages during the 
update occurred again. 

I can’t remember these messages some days ago after another installation using 
an activated root account. 

I didn’t found any issues yet. 

Anyone else got these messages?


Best
Peter


___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Fedora-Rawhide-20211109.n.0 compose check report

[Fedora compose checker]

No missing expected images.

Compose PASSES proposed Rawhide gating check!
All required tests passed

Failed openQA tests: 8/192 (x86_64), 73/141 (aarch64)

New failures (same test not failed in Fedora-Rawhide-20211108.n.0):

ID: 1058419 Test: x86_64 universal install_shrink_ntfs
URL: https://openqa.fedoraproject.org/tests/1058419
ID: 1058464 Test: aarch64 universal upgrade_server_domain_controller@uefi
URL: https://openqa.fedoraproject.org/tests/1058464
ID: 1058487 Test: aarch64 universal upgrade_realmd_client@uefi
URL: https://openqa.fedoraproject.org/tests/1058487

Old failures (same test failed in Fedora-Rawhide-20211108.n.0):

ID: 1058213 Test: x86_64 Server-dvd-iso server_cockpit_updates
URL: https://openqa.fedoraproject.org/tests/1058213
ID: 1058236 Test: x86_64 Workstation-live-iso 
desktop_notifications_postinstall
URL: https://openqa.fedoraproject.org/tests/1058236
ID: 1058242 Test: x86_64 Workstation-live-iso gedit
URL: https://openqa.fedoraproject.org/tests/1058242
ID: 1058262 Test: x86_64 KDE-live-iso apps_startstop
URL: https://openqa.fedoraproject.org/tests/1058262
ID: 1058274 Test: x86_64 KDE-live-iso desktop_notifications_postinstall
URL: https://openqa.fedoraproject.org/tests/1058274
ID: 1058299 Test: aarch64 Server-dvd-iso anaconda_help@uefi
URL: https://openqa.fedoraproject.org/tests/1058299
ID: 1058306 Test: aarch64 Server-dvd-iso support_server@uefi
URL: https://openqa.fedoraproject.org/tests/1058306
ID: 1058307 Test: aarch64 Server-dvd-iso 
install_repository_nfsiso_variation@uefi
URL: https://openqa.fedoraproject.org/tests/1058307
ID: 1058310 Test: aarch64 Server-dvd-iso install_updates_nfs@uefi
URL: https://openqa.fedoraproject.org/tests/1058310
ID: 1058319 Test: aarch64 Server-dvd-iso 
install_repository_nfs_graphical@uefi
URL: https://openqa.fedoraproject.org/tests/1058319
ID: 1058320 Test: aarch64 Server-dvd-iso 
install_repository_nfs_variation@uefi
URL: https://openqa.fedoraproject.org/tests/1058320
ID: 1058367 Test: aarch64 Workstation-raw_xz-raw.xz gedit@uefi
URL: https://openqa.fedoraproject.org/tests/1058367
ID: 1058371 Test: aarch64 Cloud_Base-qcow2-qcow2 base_selinux@uefi
URL: https://openqa.fedoraproject.org/tests/1058371
ID: 1058372 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi
URL: https://openqa.fedoraproject.org/tests/1058372
ID: 1058373 Test: aarch64 Cloud_Base-qcow2-qcow2 base_reboot_unmount@uefi
URL: https://openqa.fedoraproject.org/tests/1058373
ID: 1058374 Test: aarch64 Cloud_Base-qcow2-qcow2 base_services_start@uefi
URL: https://openqa.fedoraproject.org/tests/1058374
ID: 1058375 Test: aarch64 Cloud_Base-qcow2-qcow2 
base_package_install_remove@uefi
URL: https://openqa.fedoraproject.org/tests/1058375
ID: 1058376 Test: aarch64 Cloud_Base-qcow2-qcow2 base_system_logging@uefi
URL: https://openqa.fedoraproject.org/tests/1058376
ID: 1058377 Test: aarch64 Cloud_Base-qcow2-qcow2 
base_service_manipulation@uefi
URL: https://openqa.fedoraproject.org/tests/1058377
ID: 1058378 Test: aarch64 Cloud_Base-qcow2-qcow2 base_update_cli@uefi
URL: https://openqa.fedoraproject.org/tests/1058378
ID: 1058412 Test: x86_64 universal support_server
URL: https://openqa.fedoraproject.org/tests/1058412
ID: 1058441 Test: x86_64 universal install_iscsi
URL: https://openqa.fedoraproject.org/tests/1058441
ID: 1058463 Test: aarch64 universal upgrade_server_64bit@uefi
URL: https://openqa.fedoraproject.org/tests/1058463
ID: 1058470 Test: aarch64 universal upgrade_2_desktop_encrypted_64bit@uefi
URL: https://openqa.fedoraproject.org/tests/1058470
ID: 1058473 Test: aarch64 universal upgrade_desktop_encrypted_64bit@uefi
URL: https://openqa.fedoraproject.org/tests/1058473
ID: 1058490 Test: aarch64 universal upgrade_2_server_domain_controller@uefi
URL: https://openqa.fedoraproject.org/tests/1058490
ID: 1058504 Test: aarch64 universal upgrade_2_realmd_client@uefi
URL: https://openqa.fedoraproject.org/tests/1058504
ID: 1058507 Test: aarch64 Server-boot-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/1058507
ID: 1058508 Test: aarch64 Server-dvd-iso install_blivet_lvm_ext4@uefi
URL: https://openqa.fedoraproject.org/tests/1058508
ID: 1058509 Test: aarch64 Server-dvd-iso 
install_standard_partition_ext4@uefi
URL: https://openqa.fedoraproject.org/tests/1058509
ID: 1058510 Test: aarch64 Server-dvd-iso install_vnc_server@uefi
URL: https://openqa.fedoraproject.org/tests/1058510
ID: 1058511 Test: aarch64 Server-dvd-iso install_vnc_client@uefi
URL: https://openqa.fedoraproject.org/tests/1058511
ID: 1058512 Test: aarch64 Server-dvd-iso install_btrfs_preserve_home@uefi
URL: https://openqa.fedoraproject.org/tests/1058512
ID: 1058513 Test: aarch64 Server-dvd-iso install_lvm_ext4@uefi
URL: https://openqa.fedoraproject.org/tests/1058513
ID: 1058516 Test: aarch64 Server-dvd-iso 
install_blivet_btrfs_preserve_home_uefi@uefi
URL: https://ope

Re: Fedora 35 - gedit

[Michael J. Baars]

On Tue, 2021-11-09 at 13:00 +0100, Fabio Valentini wrote:
> On Tue, Nov 9, 2021 at 10:13 AM Michael J. Baars
>  wrote:
> > Hi All,
> > 
> > I've been working with Fedora for years now, and I just installed the 
> > newest Fedora Workstation 35 on one of my computers.
> > 
> > Since I use gedit a lot for editing source codes, gedit was one of the 
> > first programs I tried to launch. Now, there I get into trouble. After 
> > opening a few
> > source files and trying to start off where I left, I noticed that the mouse 
> > pointer (and the line number) often does not end up where I clicked the 
> > mouse
> > when
> > trying to position the cursor (for cutting and pasting for example). This 
> > is the very first time that I experience this problem.
> > 
> > Help would be appreciated,
> 
> Have you tried just updating your Fedora 35 system with the most recent 
> updates?
> Because I noticed a recent gnome-shell and mutter update that claims
> to fix jumping cursor positions in text editors:
> https://bodhi.fedoraproject.org/updates/FEDORA-2021-4ce970eca6

Nothing with 'sudo dnf upgrade --advisory=FEDORA-2021-4ce970eca6' either. It 
keeps saying: "Nothing to do"???

> Fabio
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it: 
> https://pagure.io/fedora-infrastructure
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: deltarpm usefulness?

[Demi Marie Obenour]

On 11/9/21 7:46 AM, Stephen John Smoogen wrote:
> On Tue, 9 Nov 2021 at 04:39, Rajeesh K V  wrote:
>>
 I remember seeing 60-70% reduction really often, and 90+ periodically.  
 I've
 read Kevin's explanation of why it's not working as well now, but I wonder
 what changed between the early implementation when results were very good
 and now, when they really aren't.
>>>
>>> I think it's because you only see deltas from N to N+1 now and before
>>> you saw deltas from N to N+X before. So, I think if we made it somehow
>>> create older deltas, you would again see better savings. The issue
>>> doesn't just cause there to be fewer deltas, but it also causes those
>>> few be be against very recent changes, so less effective.
>>
>> Would it make sense (and possible to implement fairly easily) to
>> generate deltas weekly instead of daily? That may already be a good
>> start; as I’d imagine bandwidth constrained users would generally try
>> to update on a weekly or monthly basis.
> 
> Not easily for 2 reasons:
> 
> 1. deltas are package to package and many packages rev 4-6 times a
> week (I am looking at you, kernel). So a once a week delta update
> would have to make deltas against each of those packages for both
> people who are resource constrained and those who are not.
> 2. Each 'compose' of Fedora is like a manufacturing line where if you
> turn off some part, the rest after that point break because something
> they expect is not there. If we turn off deltas altogether, we can
> clean up various bits that were expected afterwards but someone would
> need to do that work while doing all the usual work.
> 
> So you would need to set up a seperate compose pipeline which would do
> this once a week and put those in a tree which is distinct from the
> regular daily Fedora. That requires doubling the number of servers and
> increasing disk space. Both of which are limited resources on the part
> of Fedora Infrastructure.

Would it be possible to just stop making deltarpms entirely and disable
them outright?  It appears that this would save a significant amount of
resources on the Fedora side, and they increase the attack surface of
all Fedora users who do not disable them.

Sincerely,
Demi Marie Obenour (she/her/hers)


OpenPGP_0xB288B55FFF9C22C1.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Fedocal] Reminder meeting : Fedora Source-git SIG

[csomh]

Dear all,

You are kindly invited to the meeting:
   Fedora Source-git SIG on 2021-11-10 from 14:30:00 to 15:30:00 GMT
   At meet.google.com/mic-otnv-kse

The meeting will be about:
Meeting of the Fedora source-git SIG

Agenda:
https://pagure.io/fedora-source-git/sig/issues?tags=meeting&status=Open

SIG Info:
https://fedoraproject.org/wiki/SIGs/Source-git


Source: https://calendar.fedoraproject.org//meeting/10101/

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Fedocal] Reminder meeting : Fedora Source-git SIG

[csomh]

Dear all,

You are kindly invited to the meeting:
   Fedora Source-git SIG on 2021-11-10 from 14:30:00 to 15:30:00 GMT
   At meet.google.com/mic-otnv-kse

The meeting will be about:
Bi-weekly meeting of the Fedora source-git SIG

Agenda:
https://pagure.io/fedora-source-git/sig/issues?tags=meeting&status=Open

SIG Info:
https://fedoraproject.org/wiki/SIGs/Source-git


Source: https://calendar.fedoraproject.org//meeting/10111/

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Fedora 35 - gedit

[Vitaly Zaitsev via devel]

On 09/11/2021 14:18, Michael J. Baars wrote:

Nothing with 'sudo dnf upgrade --advisory=FEDORA-2021-4ce970eca6' either. It keeps 
saying: "Nothing to do"???


sudo dnf upgrade --refresh --advisory=FEDORA-2021-4ce970eca6 
--enablerepo=updates-testing


--
Sincerely,
  Vitaly Zaitsev (vit...@easycoding.org)
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: deltarpm usefulness?

[Frank Ch. Eigler]

kevin wrote:

> I think it's because you only see deltas from N to N+1 now and before
> you saw deltas from N to N+X before. So, I think if we made it somehow
> create older deltas, you would again see better savings. The issue
> doesn't just cause there to be fewer deltas, but it also causes those
> few be be against very recent changes, so less effective.

That should be fun to quantify.  Heck, in principle it could be possible
for a client to use a sequence of deltas to go from some random older
version to the current one (sort of like shellsort).

- FChE
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Package FFMPEG with royalty free codes (AV1, THEORA, VPX, OGG, OPUS, SPEEX, ...) for Fedora

[Robbie Harwood]

Vitaly Zaitsev via devel  writes:

> On 08/11/2021 16:47, Andreas Schneider wrote:
>> I have electron building offline for Fedora, you can find it here:
>> https://build.opensuse.org/package/show/network:im:signal/nodejs-electron
>
> Electron core packaging is a quite trivial task (Arch Linux and Debian 
> have already done this), but what about Electron applications (VS Code 
> for example)?

They have?  What's it called?  Asking because I don't see it:

rharwood@eesha:~$ aptitude search electron | grep -v electronics
p  node-electron-to-chromium - Provides a list of electron-to-chromium 
version mappings
rharwood@eesha:~$

Be well,
--Robbie


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Orphaning python-bsddb3

[Jan Staněk]

Hello all,
I'm the current maintainer for the python-bsddb3.
Recently, it FTBFS in Rawhide [1], and the upstream now considers it
deprecated [2], replaced with the `berkeleydb` python package.

[1]: https://bugzilla.redhat.com/show_bug.cgi?id=2019310
[2]: https://www.jcea.es/programacion/pybsddb.htm

I have packaged the `bsddb3` back when I was also maintainer of libdb
in Fedora. I no longer take care of it, and I'm not interested in
packaging the newer bindings. I've reached out to libdb maintainer,
and they are not interested either [3].

[3]: https://bugzilla.redhat.com/show_bug.cgi?id=2019310#c4

The only packages that require the python-bsddb3 packages seem to be:

exaile (runtime and buildtime)
gramps (runtime)
python-zarr (buildtime only)

The maintainers are CC'd; feel free to reach to me if you want to take
over python-bsddb3. If not, be advised that I intend to orphan it in a
week or two, and your package will probably need changes.

Best regards,
--
Jan Staněk
Software Engineer, Red Hat
jsta...@redhat.com   irc: jstanek


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Fedora 35 - gedit

[Michael J. Baars]

On Tue, 2021-11-09 at 15:31 +0100, Vitaly Zaitsev via devel wrote:
> On 09/11/2021 14:18, Michael J. Baars wrote:
> > Nothing with 'sudo dnf upgrade --advisory=FEDORA-2021-4ce970eca6' either. 
> > It keeps saying: "Nothing to do"???
> 
> sudo dnf upgrade --refresh --advisory=FEDORA-2021-4ce970eca6 
> --enablerepo=updates-testing
> 

Does that work on you machine??? Still nothing on mine.

Best regards,
Mischa.

> -- 
> Sincerely,
>Vitaly Zaitsev (vit...@easycoding.org)
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it: 
> https://pagure.io/fedora-infrastructure

[root@tp10 ~]# dnf upgrade --advisory=FEDORA-2021-4ce970eca6 
--enablerepo=updates-testing --refresh
Fedora 35
-x86_64 



 226 kB/s |  17 kB 00:00
Fedora 35 openh264 (From Cisco) - x86_64


  1.8
kB/s | 990  B 00:00
Fedora Modular 35 - x86_64  


   
   180 kB/s |  17 kB 00:00
Fedora 35 - x86_64 - Updates


   
26 kB/s |  18 kB 00:00
Fedora Modular 35 - x86_64 - Updates


   
48 kB/s |  18 kB 00:00
Fedora 35 - x86_64 - Test Updates   
   

   
 25 kB/s |  17 kB 00:00  
Dependencies resolved.
Nothing to do.
Complete!
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Fedora 35 - gedit

[Otto Urpelainen]

Michael J. Baars kirjoitti 9.11.2021 klo 17.56:

On Tue, 2021-11-09 at 15:31 +0100, Vitaly Zaitsev via devel wrote:

On 09/11/2021 14:18, Michael J. Baars wrote:

Nothing with 'sudo dnf upgrade --advisory=FEDORA-2021-4ce970eca6' either. It keeps 
saying: "Nothing to do"???


sudo dnf upgrade --refresh --advisory=FEDORA-2021-4ce970eca6
--enablerepo=updates-testing



Does that work on you machine??? Still nothing on mine.


Please check the package versions you have installed against the 
versions in the update. Instructions:


First, check what the update installs. In the linked Bodhi page, open 
tab Builds and check what is in there. In this case, you will see these:


gnome-shell-41.1-1.fc35
mutter-41.1-1.fc35

Then check your local versions:

$ dnf -C info --installed gnome-shell mutter

If you see "Version: 41.1" and "Release: 1.fc35" for both of these, then 
you have the update already. That would explain why dnf says nothing to do.


Otto
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Fedora 35 - gedit

[Michael J. Baars]

Hi,

This update can't be installed because the update is already in the Fedora 35 
release version, according to 
https://bodhi.fedoraproject.org/updates/FEDORA-2021-4ce970eca6.

I still have the dancing mouse pointer and cursor though :(

I'll place a notice of this on 
https://bugzilla.redhat.com/show_bug.cgi?id=2017192 first thing tomorrow.

Best regards,
Mischa.

On Tue, 2021-11-09 at 15:31 +0100, Vitaly Zaitsev via devel wrote:
> On 09/11/2021 14:18, Michael J. Baars wrote:
> > Nothing with 'sudo dnf upgrade --advisory=FEDORA-2021-4ce970eca6' either. 
> > It keeps saying: "Nothing to do"???
> 
> sudo dnf upgrade --refresh --advisory=FEDORA-2021-4ce970eca6 
> --enablerepo=updates-testing
> 
> -- 
> Sincerely,
>Vitaly Zaitsev (vit...@easycoding.org)
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it: 
> https://pagure.io/fedora-infrastructure
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Fedora 35 - gedit

[Michael J. Baars]

On Tue, 2021-11-09 at 18:03 +0200, Otto Urpelainen wrote:
> Michael J. Baars kirjoitti 9.11.2021 klo 17.56:
> > On Tue, 2021-11-09 at 15:31 +0100, Vitaly Zaitsev via devel wrote:
> > > On 09/11/2021 14:18, Michael J. Baars wrote:
> > > > Nothing with 'sudo dnf upgrade --advisory=FEDORA-2021-4ce970eca6' 
> > > > either. It keeps saying: "Nothing to do"???
> > > 
> > > sudo dnf upgrade --refresh --advisory=FEDORA-2021-4ce970eca6
> > > --enablerepo=updates-testing
> > > 
> > 
> > Does that work on you machine??? Still nothing on mine.
> 
> Please check the package versions you have installed against the 
> versions in the update. Instructions:
> 
> First, check what the update installs. In the linked Bodhi page, open 
> tab Builds and check what is in there. In this case, you will see these:
> 
>  gnome-shell-41.1-1.fc35
>  mutter-41.1-1.fc35
> 
> Then check your local versions:
> 
>  $ dnf -C info --installed gnome-shell mutter
> 
> If you see "Version: 41.1" and "Release: 1.fc35" for both of these, then 
> you have the update already. That would explain why dnf says nothing to do.

Exactly! Then it has nothing to do. Yet, I still observe the dancing mouse 
pointer and cursor. It's quite annoying indeed... I can't possibly do any 
programming
like this either :)

> 
> Otto
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it: 
> https://pagure.io/fedora-infrastructure
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Fedora 35 - gedit

[Adam Williamson]

On Tue, 2021-11-09 at 16:56 +0100, Michael J. Baars wrote:
> On Tue, 2021-11-09 at 15:31 +0100, Vitaly Zaitsev via devel wrote:
> > On 09/11/2021 14:18, Michael J. Baars wrote:
> > > Nothing with 'sudo dnf upgrade --advisory=FEDORA-2021-4ce970eca6' either. 
> > > It keeps saying: "Nothing to do"???
> > 
> > sudo dnf upgrade --refresh --advisory=FEDORA-2021-4ce970eca6 
> > --enablerepo=updates-testing
> > 
> 
> Does that work on you machine??? Still nothing on mine.

To pick up from the update thread, it seems you found you already have
these updates installed. To check one more thing, though, have you
logged out since installing them? The bug will persist until you do.

If you have them installed and you've logged out or rebooted since
installing them, then there's clearly still an issue, but we'll likely
need more information to fix it. It would help if you can identify a
precise sequence of steps - starting from a clean desktop - that
reliably reproduces the problem for you. Thanks!
-- 
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: During the first update after installation: Failed to connect to bus: Invalid argument

[Adam Williamson]

On Tue, 2021-11-09 at 14:06 +0100, Peter Boy wrote:
> While updating right after installation of Fedora Server 35 today I get:
> 
> > [...]# sudo  dnf  update
> >   ...
> >   Cleanup  : glibc-langpack-de-2.34-7.fc35.x86_64   
> > 303/306 
> >   Cleanup  : glibc-gconv-extra-2.34-7.fc35.x86_64   
> > 304/306 
> >   Running Scriptlet: glibc-gconv-extra-2.34-7.fc35.x86_64   
> > 304/306 
> >   Cleanup  : glibc-common-2.34-7.fc35.x86_64
> > 305/306 
> >   Cleanup  : tzdata-2021b-1.fc35.noarch 
> > 306/306 
> >   Running Scriptlet: grub2-common-1:2.06-8.fc35.noarch  
> > 306/306 
> >   Running Scriptlet: selinux-policy-targeted-35.5-1.fc35.noarch 
> > 306/306 
> >   Running Scriptlet: clevis-18-4.fc35.x86_64
> > 306/306 
> >   Running Scriptlet: libwbclient-2:4.15.1-0.fc35.x86_64 
> > 306/306 
> >   Running Scriptlet: kernel-core-5.14.16-301.fc35.x86_64
> > 306/306 
> >   Running Scriptlet: sssd-common-2.6.0-2.fc35.x86_64
> > 306/306 
> >   Running Scriptlet: tzdata-2021b-1.fc35.noarch 
> > 306/306 
> > Failed to connect to bus: Invalid argument
> > 
> > Failed to connect to bus: Invalid argument
> > 
> > Failed to connect to bus: Invalid argument
> > Failed to connect to bus: Invalid argument
> > 
> >   Verifying: clevis-pin-tpm2-0.3.0-2.fc35.x86_64
> >   1/306 
> >   Verifying: freetype-2.11.0-1.fc35.x86_64  
> >   2/306 
> 
> 
> I first suspected there was an error during installation and repeated it, 
> watching for error / warning messages (none). The error messages during the 
> update occurred again. 
> 
> I can’t remember these messages some days ago after another installation 
> using an activated root account. 
> 
> I didn’t found any issues yet. 
> 
> Anyone else got these messages?

Yeah, some standard %post script is triggering it most likely. I see it
frequently in Rawhide updates. It's most likely one of the systemd
scriptlets that calls /usr/lib/systemd/systemd-update-helper . I dunno
if anyone's filed a bug on it yet.
-- 
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Fedora 35 - gedit

[Michael J. Baars]

Hi Adam,

I didn't install any update, apparently the update is already included with
the release version of Fedora 35, because it won't install from the command
line and the versions from the build match the versions from the release.
This is a fresh installation of Fedora 35 Workstation, done the day before
yesterday.

So, with the updates INCLUDED instead of installed, the mouse pointer and
the cursor (still) act strange when running gedit. When I try to move the
mouse into position and click to move the cursor into position, for example
to cut and past text, both OFTEN (say 50% of these attempts) end up on a
completely different line number, sometimes even selecting some text in the
process.

The updates as provided by the build and as included in the release version
of Fedora 35, do therefore not function as intended.

Precise sequence of steps:
1) turn on computer
2) open text files from file manager
3) start editing

Nothing more, nothing less, nothing out of the ordinary either. The problem
had never reveiled itself on another one of my computers, which is still
running Fedora 32 Workstation. It's definitely new, impossible to overlook,
and impossible to ignore when your used to working with gedit as your
default editor as I am.

Best regards,
Mischa Baars.


On Tue, 9 Nov 2021, 17:50 Adam Williamson, 
wrote:

> On Tue, 2021-11-09 at 16:56 +0100, Michael J. Baars wrote:
> > On Tue, 2021-11-09 at 15:31 +0100, Vitaly Zaitsev via devel wrote:
> > > On 09/11/2021 14:18, Michael J. Baars wrote:
> > > > Nothing with 'sudo dnf upgrade --advisory=FEDORA-2021-4ce970eca6'
> either. It keeps saying: "Nothing to do"???
> > >
> > > sudo dnf upgrade --refresh --advisory=FEDORA-2021-4ce970eca6
> > > --enablerepo=updates-testing
> > >
> >
> > Does that work on you machine??? Still nothing on mine.
>
> To pick up from the update thread, it seems you found you already have
> these updates installed. To check one more thing, though, have you
> logged out since installing them? The bug will persist until you do.
>
> If you have them installed and you've logged out or rebooted since
> installing them, then there's clearly still an issue, but we'll likely
> need more information to fix it. It would help if you can identify a
> precise sequence of steps - starting from a clean desktop - that
> reliably reproduces the problem for you. Thanks!
> --
> Adam Williamson
> Fedora QA
> IRC: adamw | Twitter: adamw_ha
> https://www.happyassassin.net
>
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: During the first update after installation: Failed to connect to bus: Invalid argument

[Richard W.M. Jones]

On Tue, Nov 09, 2021 at 02:06:54PM +0100, Peter Boy wrote:
> While updating right after installation of Fedora Server 35 today I get:
> 
> > [...]# sudo  dnf  update
> >   ...
> >   Cleanup  : glibc-langpack-de-2.34-7.fc35.x86_64   
> > 303/306 
> >   Cleanup  : glibc-gconv-extra-2.34-7.fc35.x86_64   
> > 304/306 
> >   Running Scriptlet: glibc-gconv-extra-2.34-7.fc35.x86_64   
> > 304/306 
> >   Cleanup  : glibc-common-2.34-7.fc35.x86_64
> > 305/306 
> >   Cleanup  : tzdata-2021b-1.fc35.noarch 
> > 306/306 
> >   Running Scriptlet: grub2-common-1:2.06-8.fc35.noarch  
> > 306/306 
> >   Running Scriptlet: selinux-policy-targeted-35.5-1.fc35.noarch 
> > 306/306 
> >   Running Scriptlet: clevis-18-4.fc35.x86_64
> > 306/306 
> >   Running Scriptlet: libwbclient-2:4.15.1-0.fc35.x86_64 
> > 306/306 
> >   Running Scriptlet: kernel-core-5.14.16-301.fc35.x86_64
> > 306/306 
> >   Running Scriptlet: sssd-common-2.6.0-2.fc35.x86_64
> > 306/306 
> >   Running Scriptlet: tzdata-2021b-1.fc35.noarch 
> > 306/306 
> > Failed to connect to bus: Invalid argument
> > 
> > Failed to connect to bus: Invalid argument
> > 
> > Failed to connect to bus: Invalid argument
> > Failed to connect to bus: Invalid argument
> > 
> >   Verifying: clevis-pin-tpm2-0.3.0-2.fc35.x86_64
> >   1/306 
> >   Verifying: freetype-2.11.0-1.fc35.x86_64  
> >   2/306 
> 
> 
> I first suspected there was an error during installation and repeated it, 
> watching for error / warning messages (none). The error messages during the 
> update occurred again. 
> 
> I can’t remember these messages some days ago after another installation 
> using an activated root account. 
> 
> I didn’t found any issues yet. 
> 
> Anyone else got these messages?

Yes.  I ignored them because they had no obvious effect on anything.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-top is 'top' for virtual machines.  Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: During the first update after installation: Failed to connect to bus: Invalid argument

[Fabio Valentini]

On Tue, Nov 9, 2021 at 5:53 PM Adam Williamson
 wrote:
>
> On Tue, 2021-11-09 at 14:06 +0100, Peter Boy wrote:
> > While updating right after installation of Fedora Server 35 today I get:
> >
> > > [...]# sudo  dnf  update
> > >   ...
> > >   Cleanup  : glibc-langpack-de-2.34-7.fc35.x86_64 
> > >   303/306
> > >   Cleanup  : glibc-gconv-extra-2.34-7.fc35.x86_64 
> > >   304/306
> > >   Running Scriptlet: glibc-gconv-extra-2.34-7.fc35.x86_64 
> > >   304/306
> > >   Cleanup  : glibc-common-2.34-7.fc35.x86_64  
> > >   305/306
> > >   Cleanup  : tzdata-2021b-1.fc35.noarch   
> > >   306/306
> > >   Running Scriptlet: grub2-common-1:2.06-8.fc35.noarch
> > >   306/306
> > >   Running Scriptlet: selinux-policy-targeted-35.5-1.fc35.noarch   
> > >   306/306
> > >   Running Scriptlet: clevis-18-4.fc35.x86_64  
> > >   306/306
> > >   Running Scriptlet: libwbclient-2:4.15.1-0.fc35.x86_64   
> > >   306/306
> > >   Running Scriptlet: kernel-core-5.14.16-301.fc35.x86_64  
> > >   306/306
> > >   Running Scriptlet: sssd-common-2.6.0-2.fc35.x86_64  
> > >   306/306
> > >   Running Scriptlet: tzdata-2021b-1.fc35.noarch   
> > >   306/306
> > > Failed to connect to bus: Invalid argument
> > >
> > > Failed to connect to bus: Invalid argument
> > >
> > > Failed to connect to bus: Invalid argument
> > > Failed to connect to bus: Invalid argument
> > >
> > >   Verifying: clevis-pin-tpm2-0.3.0-2.fc35.x86_64  
> > > 1/306
> > >   Verifying: freetype-2.11.0-1.fc35.x86_64
> > > 2/306
> >
> >
> > I first suspected there was an error during installation and repeated it, 
> > watching for error / warning messages (none). The error messages during the 
> > update occurred again.
> >
> > I can’t remember these messages some days ago after another installation 
> > using an activated root account.
> >
> > I didn’t found any issues yet.
> >
> > Anyone else got these messages?
>
> Yeah, some standard %post script is triggering it most likely. I see it
> frequently in Rawhide updates. It's most likely one of the systemd
> scriptlets that calls /usr/lib/systemd/systemd-update-helper . I dunno
> if anyone's filed a bug on it yet.

Yes, there's been multiple bug reports filed for this:
https://bugzilla.redhat.com/show_bug.cgi?id=2020415

And as you suspected, it's a problem in systemd RPM scriptlet helper scripts.

Fabio
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

: [Errno 13] Permission denied: '/mnt/koji/work'

[Richard W.M. Jones]

https://koji.fedoraproject.org/koji/taskinfo?taskID=78586013

I kicked off a new build just now to see if it's repeatable:

https://koji.fedoraproject.org/koji/taskinfo?taskID=78587217

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
libguestfs lets you edit virtual machines.  Supports shell scripting,
bindings from many languages.  http://libguestfs.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: : [Errno 13] Permission denied: '/mnt/koji/work'

[Miro Hrončok]

On 09. 11. 21 20:31, Richard W.M. Jones wrote:


https://koji.fedoraproject.org/koji/taskinfo?taskID=78586013

I kicked off a new build just now to see if it's repeatable:

https://koji.fedoraproject.org/koji/taskinfo?taskID=78587217


See https://status.fedoraproject.org/ -- there is a Koji outage in progress.

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Notice: openQA test failures today - expected

[Adam Williamson]

Hey folks! Just a heads up about test failures in openQA overnight and
today. The server_cockpit_updates test was failing overnight; this was
because I switched from virtio to qxl graphics to work around a bug in
Rawhide. Unfortunately there seems to be a bug in qxl with a specific
thing that test does (snapshot the machine, run X from a console,
restore the snapshot, run X from a console again).

I've switched that test back to virtio graphics and re-triggered all
the failed runs, but since then the planned Koji outage has started.
All update tests that run during the Koji outage will fail because the
test process relies on downloading the update packages from Koji. So
some of the re-runs for the other bug failed. We will not be able to
get successful runs until the Koji outage is over.

Basically, if you're seeing an openQA failure on your update, hang
tight for the end of the Koji outage.

There are two updates with other issues (a Pango update that changes
font rendering and so will need a lot of openQA screenshots to be re-
taken, and a Python update that seems to break `systemctl stop
ipa.service` for some reason), but again I can't really work on those
with Koji down, so will wait for it to be back.

Thanks folks!
-- 
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net

___
devel-announce mailing list -- devel-annou...@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-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/devel-annou...@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Fedora 35 - gedit

[Adam Williamson]

On Tue, 2021-11-09 at 18:59 +0100, Michael J. Baars wrote:
> Hi Adam,
> 
> I didn't install any update, apparently the update is already included with
> the release version of Fedora 35, because it won't install from the command
> line and the versions from the build match the versions from the release.
> This is a fresh installation of Fedora 35 Workstation, done the day before
> yesterday.
> 
> So, with the updates INCLUDED instead of installed, the mouse pointer and
> the cursor (still) act strange when running gedit. When I try to move the
> mouse into position and click to move the cursor into position, for example
> to cut and past text, both OFTEN (say 50% of these attempts) end up on a
> completely different line number, sometimes even selecting some text in the
> process.
> 
> The updates as provided by the build and as included in the release version
> of Fedora 35, do therefore not function as intended.
> 
> Precise sequence of steps:
> 1) turn on computer
> 2) open text files from file manager
> 3) start editing
> 
> Nothing more, nothing less, nothing out of the ordinary either. The problem
> had never reveiled itself on another one of my computers, which is still
> running Fedora 32 Workstation. It's definitely new, impossible to overlook,
> and impossible to ignore when your used to working with gedit as your
> default editor as I am.

Thanks. So:

1. That update was not included in the release. The update was created
on 2021-11-04, which is *after* the release happened (on 2021-11-02),
let alone when the release was signed off (2021-10-28) or actually
built (I think that was 2021-10-25). The release has gnome-shell-41.0-
4.fc35 and mutter-41.0-4.fc35 . You can see this for yourself at 
https://dl.fedoraproject.org/pub/fedora/linux/releases/35/Everything/x86_64/os/Packages/g/
and
https://dl.fedoraproject.org/pub/fedora/linux/releases/35/Everything/x86_64/os/Packages/m/
. This is just a note, as long as you have the updated versions and
have rebooted since installing them, it doesn't really matter where you
got them.

2. The problem you are having is not the problem the update was
intended to fix. I know this because I was the person who noticed the
problem and backported the fix. That problem did not occur simply by
opening a file and editing it, it always involved switching focus
between the text editor and other windows. There are more details on
the bug the update actually fixes at
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4647 . The update
definitely did fix that problem, because I had it before and I don't
have it now.

3. The problem you're hitting now is not likely a general one, or else
a lot more people would likely be complaining about it, given how
"impossible to overlook" (your words) it is. It's not happening to me,
for instance. gedit behaves just fine for me. Unless anyone else can
reproduce it by just running gedit, we still need to figure out what
exactly in your configuration is triggering the problem. Maybe you
could record a video of it? That might show something that helps.

Thanks!
-- 
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Fedora 35 - gedit

[Stephen Snow]

I cannot get Gedit to do this when I use it as a text editor, even for
extended periods with intermittent thrashing, like loads of edits
without a save, etc...

It does sound almost hardware specific, maybe failing keyboard.?

Stephen

On Tue, 2021-11-09 at 12:49 -0800, Adam Williamson wrote:
> On Tue, 2021-11-09 at 18:59 +0100, Michael J. Baars wrote:
> > Hi Adam,
> > 
> > I didn't install any update, apparently the update is already
> > included with
> > the release version of Fedora 35, because it won't install from the
> > command
> > line and the versions from the build match the versions from the
> > release.
> > This is a fresh installation of Fedora 35 Workstation, done the day
> > before
> > yesterday.
> > 
> > So, with the updates INCLUDED instead of installed, the mouse
> > pointer and
> > the cursor (still) act strange when running gedit. When I try to
> > move the
> > mouse into position and click to move the cursor into position, for
> > example
> > to cut and past text, both OFTEN (say 50% of these attempts) end up
> > on a
> > completely different line number, sometimes even selecting some
> > text in the
> > process.
> > 
> > The updates as provided by the build and as included in the release
> > version
> > of Fedora 35, do therefore not function as intended.
> > 
> > Precise sequence of steps:
> > 1) turn on computer
> > 2) open text files from file manager
> > 3) start editing
> > 
> > Nothing more, nothing less, nothing out of the ordinary either. The
> > problem
> > had never reveiled itself on another one of my computers, which is
> > still
> > running Fedora 32 Workstation. It's definitely new, impossible to
> > overlook,
> > and impossible to ignore when your used to working with gedit as
> > your
> > default editor as I am.
> 
> Thanks. So:
> 
> 1. That update was not included in the release. The update was
> created
> on 2021-11-04, which is *after* the release happened (on 2021-11-02),
> let alone when the release was signed off (2021-10-28) or actually
> built (I think that was 2021-10-25). The release has gnome-shell-
> 41.0-
> 4.fc35 and mutter-41.0-4.fc35 . You can see this for yourself at 
> https://dl.fedoraproject.org/pub/fedora/linux/releases/35/Everything/x86_64/os/Packages/g/
> and
> https://dl.fedoraproject.org/pub/fedora/linux/releases/35/Everything/x86_64/os/Packages/m/
> . This is just a note, as long as you have the updated versions and
> have rebooted since installing them, it doesn't really matter where
> you
> got them.
> 
> 2. The problem you are having is not the problem the update was
> intended to fix. I know this because I was the person who noticed the
> problem and backported the fix. That problem did not occur simply by
> opening a file and editing it, it always involved switching focus
> between the text editor and other windows. There are more details on
> the bug the update actually fixes at
> https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4647 . The update
> definitely did fix that problem, because I had it before and I don't
> have it now.
> 
> 3. The problem you're hitting now is not likely a general one, or
> else
> a lot more people would likely be complaining about it, given how
> "impossible to overlook" (your words) it is. It's not happening to
> me,
> for instance. gedit behaves just fine for me. Unless anyone else can
> reproduce it by just running gedit, we still need to figure out what
> exactly in your configuration is triggering the problem. Maybe you
> could record a video of it? That might show something that helps.
> 
> Thanks!
> -- 
> Adam Williamson
> Fedora QA
> IRC: adamw | Twitter: adamw_ha
> https://www.happyassassin.net
> 
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Introduction: nedia, a Silverblue fan

[przemek klosowski via devel]

Kia ora to you, and welcome to Fedora!

I hope you find something interesting to contribute in.

p

On 10/27/21 23:30, Aiden Langley wrote:

Kia ora koutou,

I'm nedia, I live in NZ & I've been knocking about the matrix/irc for a few days now. 
I'll be 28 on the 30th, I've been using Fedora for about a year, Linux for about 3-4 
(Ubuntu & Antergos), & have been doing software dev for about 5-6 years.

I started my career w/ Java, then spent some time w/ PHP on some legacy 
spaghetti, wrote a cool CLI that interfaced w/ AWS EC2 instances to run data 
conversions and had a lot of fun with it, and I've dabbled in some Rust, C#, 
Python and more JavaScript than I'd like to admit. Keen to write something in 
Go one day.

https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwowhub.co.nz%2F&data=04%7C01%7Cprzemek.klosowski%40nist.gov%7C7025d32558d449f8f6ac08d999c3812c%7C2ab5d82fd8fa4797a93e054655c61dec%7C1%7C0%7C637709887232061405%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=oMBt8wN4QxqHp1cx%2FGlh2HgpXwXfOCs8hUg2pq38O80%3D&reserved=0
 is what keeps me occupied at the moment, I  contract / volunteer at a not for profit, charge 
enough to pay my bills but my work is mostly kōha (a gift \ given free of charge.) I could 
potentially spend a lot of time on Fedora related projects, my weekends are v open & I give 
the Whakaoranga Whanau about 24 hours a week. I have tourettes so sometimes I need days to 
myself to recoup mentally.

I'm currently using Silverblue, I'm enamored by the ideas - immutability is 
huge to me now. I get anxiety whenever I use another distro, knowing one false 
step might lead to a re-install. I'm a tinkerer so it happens a fair bit.

I'm also running Rawhide, since Silverblue affords me an extra layer of 
security, it seemed like it was the perfect fit for running some potentially 
unstable software.

An area that seems like it could use some work from what I've observed is 
`rpm-ostree`, being able to upgrade packages for testing e.g. `sudo dnf upgrade 
--enablerepo=updates-testing --advisory=FEDORA-2021-992e409289` & group 
installs are missing at the moment. I wanted to be able to run a 2nd DE in case of 
bugs, but would have to install each package individually as it stands so I settle 
for just rebasing when the time comes. Is `rpm-ostree module` intended to be the 
new `group`?

Anyway, v interested in Silverblue and putting myself in a position to test & 
contribute to the above, so if anybody would like to sponsor / point me in the 
right direction, that would be much appreciated.

Cheers,
*nedia*
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.fedoraproject.org%2Fen-US%2Fproject%2Fcode-of-conduct%2F&data=04%7C01%7Cprzemek.klosowski%40nist.gov%7C7025d32558d449f8f6ac08d999c3812c%7C2ab5d82fd8fa4797a93e054655c61dec%7C1%7C0%7C637709887232061405%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=5y2U6lGEbT3d%2BNJTAIHKZsb9kX81MIVxamCXghck4Jo%3D&reserved=0
List Guidelines: 
https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffedoraproject.org%2Fwiki%2FMailing_list_guidelines&data=04%7C01%7Cprzemek.klosowski%40nist.gov%7C7025d32558d449f8f6ac08d999c3812c%7C2ab5d82fd8fa4797a93e054655c61dec%7C1%7C0%7C637709887232061405%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=lf24U63zSdKy8fxkZ9VtgCfFcK8Yf0paAsZFGSdm7A4%3D&reserved=0
List Archives: 
https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.fedoraproject.org%2Farchives%2Flist%2Fdevel%40lists.fedoraproject.org&data=04%7C01%7Cprzemek.klosowski%40nist.gov%7C7025d32558d449f8f6ac08d999c3812c%7C2ab5d82fd8fa4797a93e054655c61dec%7C1%7C0%7C637709887232061405%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=2vc9mwUgvKMNbUYRU8kj4Y0KTfXoUpvUU6iLFcJUCdA%3D&reserved=0
Do not reply to spam on the list, report it: 
https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpagure.io%2Ffedora-infrastructure&data=04%7C01%7Cprzemek.klosowski%40nist.gov%7C7025d32558d449f8f6ac08d999c3812c%7C2ab5d82fd8fa4797a93e054655c61dec%7C1%7C0%7C637709887232061405%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=wTIOARwqQs%2Fgr8GfNdVZ4JcRIwuSbBOcasxpVHG8saI%3D&reserved=0

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/ar

Re: Long-running side tag for porting Fedora to C99 (no implicit decls)

[Kevin Fenzi]

On Tue, Nov 09, 2021 at 10:41:16AM +0100, Florian Weimer wrote:
> * Kevin Fenzi:
> 
> > Isn't this an ideal use case for copr?
> 
> I don't know.  I could piece together the Koji API fairly easily, and
> had hoped to reuse some of the script logic.
> 
> Or does COPR have direct support this?  Can I tell it directly to report
> rawhide in a special buildroot?  Is there a programmatic way to access
> the resulting log files?
> 
> (I won't need the built RPMs, which is why I would use scratch builds in
> Koji.)

Yes, copr has a api also. 
https://python-copr.readthedocs.io/en/latest/ClientV3.html

> > Or is the lack of s390x (and non emulated armv7) there too much of a hurdle?
> 
> I would prefer to test on the real thing, true.

Yeah, thats the one reason I was wondering about suggesting copr, but
other than the arch issues I think it may be a better fit for this. 

kevin


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Package FFMPEG with royalty free codes (AV1, THEORA, VPX, OGG, OPUS, SPEEX, ...) for Fedora

[Maxwell G (@gotmax23) via devel]

Nov 9, 2021 9:06:58 AM Robbie Harwood :

> Vitaly Zaitsev via devel  writes:
> 
>> On 08/11/2021 16:47, Andreas Schneider wrote:
>>> I have electron building offline for Fedora, you can find it here:
>>> https://build.opensuse.org/package/show/network:im:signal/nodejs-electron
>> 
>> Electron core packaging is a quite trivial task (Arch Linux and Debian
>> have already done this), but what about Electron applications (VS Code
>> for example)?
> 
> They have?  What's it called?  Asking because I don't see it:
> 
>     rharwood@eesha:~$ aptitude search electron | grep -v electronics
>     p  node-electron-to-chromium - Provides a list of electron-to-chromium 
> version mappings
>     rharwood@eesha:~$
> 
> Be well,
> --Robbie
Hi Robbie,

It looks like you're right. According to pkgs.org[1], Electron is only packaged 
in Archlinux, Tumbleweed, and a couple more obscure distros (or at least 
obscure to me 😀).

Thanks,
Maxwell

[1]: https://pkgs.org/search/?q=electron
--
Maxwell G (@gotmax23)
Pronouns: He/Him/His
PGP Key Fingerprint: f57c76e5a238fe0a628e2ecef79e4e25e8c661f8
gotmax@e.email


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: During the first update after installation: Failed to connect to bus: Invalid argument

[Sam Varshavchik]

Peter Boy writes:


While updating right after installation of Fedora Server 35 today I get:

>   Running Scriptlet:  
tzdata-2021b-1.fc35.noarch 306/306

> Failed to connect to bus: Invalid argument
>
> Failed to connect to bus: Invalid argument
>
> Failed to connect to bus: Invalid argument
> Failed to connect to bus: Invalid argument
>
>   Verifying: clevis-pin- 




I didn’t found any issues yet.

Anyone else got these messages?


Yes. Multiple bugs were filed. They are being closed as dupes of 2020415.

The bug was opened for a different problem. Once it was fixed, this spam  
started showing up. This bug was reopened.


Who knows what spam will show up after this bug gets fixed…



pgps4XOm6wWKi.pgp
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: During the first update after installation: Failed to connect to bus: Invalid argument

[Maxwell G via devel]

On Tue, 2021-11-09 at 18:30 -0500, Sam Varshavchik wrote:
> The bug was opened for a different problem. Once it was fixed, this
> spam  
> started showing up. This bug was reopened.
> 
> Who knows what spam will show up after this bug gets fixed…
> 
Hi Sam,

The bug was just not fixed properly in the first place. It looks like
@zbyszek pushed a fix to s.fp.o[1], but they have not yet pushed the
update to Bodhi.

Thanks,
Maxwell

[1]:
https://src.fedoraproject.org/rpms/systemd/c/5326f0bf63e944024d6aafa1debf857ac3656078?branch=f35

-- 
Maxwell G
Pronouns: He/Him/His
gotmax@e.email

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: During the first update after installation: Failed to connect to bus: Invalid argument

[Maxwell G via devel]

Hi everyone,

On Tue, 2021-11-09 at 17:55 -0600, Maxwell G via devel wrote:
> On Tue, 2021-11-09 at 18:30 -0500, Sam Varshavchik wrote:
> > The bug was opened for a different problem. Once it was fixed, this
> > spam  
> > started showing up. This bug was reopened.
> > 
> > Who knows what spam will show up after this bug gets fixed…
> > 
> Hi Sam,
> 
> The bug was just not fixed properly in the first place. It looks like
> @zbyszek pushed a fix to s.fp.o[1], but they have not yet pushed the
> update to Bodhi.
> 
> Thanks,
> Maxwell
> 
> [1]:
> https://src.fedoraproject.org/rpms/systemd/c/5326f0bf63e944024d6aafa1debf857ac3656078?branch=f35

It is possible that I'm missing something (I'm not super knowledgeable
in this area). Please let me know if that's the case. I tried
rebuilding the systemd packages with that patch using mock. I am now
getting a different error message.

``` console
  Running scriptlet: syncthing-1.18.4-1.fc35.x86_64 

 2/2 
Failed to start transient service unit: Connection reset by peer
Failed to set unit properties on syncthing.service: Transport endpoint is not 
connected

Failed to start transient service unit: Connection reset by peer
Failed to reload daemon: Transport endpoint is not connected
Failed to start transient service unit: Connection reset by peer
Failed to start jobs: Transport endpoint is not connected

Failed to start transient service unit: Connection reset by peer
Failed to reload daemon: Transport endpoint is not connected

Failed to start transient service unit: Connection reset by peer
Failed to start jobs: Transport endpoint is not connected
```

Thanks,
Maxwell

-- 
Maxwell G
Pronouns: He/Him/His
gotmax@e.email


___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Bugzilla Email Notifications

[Maxwell G (@gotmax23) via devel]

Hi,

Does anyone know if it's possible to set bugzilla.redhat.com to email me a copy 
of new bugs or comments that I create?

Thanks,
Maxwell
--
Maxwell G (@gotmax23)
Pronouns: He/Him/His
PGP Key Fingerprint: f57c76e5a238fe0a628e2ecef79e4e25e8c661f8
gotmax@e.email


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Bugzilla Email Notifications

[Yaakov Selkowitz]

On Wed, 2021-11-10 at 03:56 +, Maxwell G (@gotmax23) via devel wrote:
> Does anyone know if it's possible to set bugzilla.redhat.com to email me a
> copy of new bugs or comments that I create?

Try: https://bugzilla.redhat.com/userprefs.cgi?tab=email

Then in the "The change was made by me" row, unclick the relevant boxes (e.g.
Reporter and CCed).

-- 
Yaakov Selkowitz
Senior Software Engineer - Platform Enablement
Red Hat, Inc.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Package FFMPEG with royalty free codes (AV1, THEORA, VPX, OGG, OPUS, SPEEX, ...) for Fedora

[Andreas Schneider]

On Tuesday, November 9, 2021 10:28:12 AM CET Vitaly Zaitsev via devel wrote:
> On 08/11/2021 16:47, Andreas Schneider wrote:
> 
> > I have electron building offline for Fedora, you can find it here:
> > https://build.opensuse.org/package/show/network:im:signal/nodejs-electron
> 
> 
> Electron core packaging is a quite trivial task (Arch Linux and Debian 
> have already done this), but what about Electron applications (VS Code 
> for example)?

As I've done the packaging, I strongly disagree!
 
> Most of them download tons of bundled JS blobs from npm during the 
> build. I don't think it will be easy (or even possible) to build 
> everything from sources.

Can you point me to those tons of bundled JS blobs in the source tarball from 
the above link please? I don't see them.


Thanks for your help!


Andreas

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Package FFMPEG with royalty free codes (AV1, THEORA, VPX, OGG, OPUS, SPEEX, ...) for Fedora

[Andreas Schneider]

On Monday, November 8, 2021 6:04:12 PM CET Kevin Kofler via devel wrote:
> Andreas Schneider wrote:
> 
> > I have electron building offline for Fedora, you can find it here:
> > 
> > https://build.opensuse.org/package/show/network:im:signal/nodejs-electron
> 
> 
> I see from the presence of electron-13-openh264-format-security.patch that 
> you are building the bundled OpenH264.

Oh, good catch. I've removed it from the source tarball and disabled it.

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Fedora-Cloud-33-20211110.0 compose check report

[Fedora compose checker]

No missing expected images.

Soft failed openQA tests: 1/8 (x86_64), 1/8 (aarch64)
(Tests completed, but using a workaround for a known bug)

Old soft failures (same test soft failed in Fedora-Cloud-33-20211109.0):

ID: 1059220 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://openqa.fedoraproject.org/tests/1059220
ID: 1059229 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi
URL: https://openqa.fedoraproject.org/tests/1059229

Passed openQA tests: 7/8 (x86_64), 7/8 (aarch64)
-- 
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Package FFMPEG with royalty free codes (AV1, THEORA, VPX, OGG, OPUS, SPEEX, ...) for Fedora

[Vitaly Zaitsev via devel]

On 10/11/2021 08:01, Andreas Schneider wrote:

Can you point me to those tons of bundled JS blobs in the source tarball from
the above link please? I don't see them.


https://github.com/microsoft/vscode/blob/main/yarn.lock - 11K lines of 
external dependencies.


All of them must be compiled from source on Fedora's infra.

--
Sincerely,
  Vitaly Zaitsev (vit...@easycoding.org)
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure