Re: Announcing fmt library soversion bump

[Aleksei Bavshin]

On 7/11/22 09:50, Ben Beasley wrote:
Two of the three packages I tried to rebuild (bear and fmidi) failed 
with errors like:


/usr/include/fmt/core.h:1733:7: error: static assertion failed: Cannot format an 
argument. To make type T formattable provide a formatter 
specialization:https://fmt.dev/latest/api.html#udt
  1733 |   formattable,
   |   ^~~

Links to failing scratch builds in the side tag:

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

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

I found that there was already a bug report open upstream for Bear: 
https://github.com/rizsotto/Bear/issues/471


Thanks for bringing attention to that. I suspect the following fmt 
changelog entry:


"Disabled automatic std::ostream insertion operator (operator<<) 
discovery when fmt/ostream.h is included to prevent ODR violations. You 
can get the old behavior by defining FMT_DEPRECATED_OSTREAM but this 
will be removed in the next major release. Use fmt::streamed or 
fmt::ostream_formatter to enable formatting via std::ostream instead."


That is a VERY breaking change and there will be more packages affected. 
It's likely also affecting dependents of spdlog which use external fmt 
and .


The fix is simple, but not backward-compatible:
   template <> struct fmt::formatter : ostream_formatter {};
(a custom fmt::formatter for the type would work as well).

I already confirmed that `waybar` is broken and will submit a fix 
upstream when I have time. Setting up a copr repo to find all other 
breakages sounds like a good idea.
If that FTBFS rate is typical of the full set of affected packages, then 
merging the side tag without resolving the API incompatibilities in 
dependent packages will be pretty disruptive to Rawhide as a whole.


Would you consider setting up a COPR to figure out how many packages are 
affected by the API changes, and filing Bugzillas on the affected 
dependent packages? It might take a while for affected package 
maintainers to become aware of the problem, investigate, and perhaps 
work with upstreams to prepare the necessary patches.


Link to fmt 9.0.0 release notes: 
https://github.com/fmtlib/fmt/releases/tag/9.0.0


– Ben

On 7/11/22 12:21, Ben Beasley wrote:


I don’t believe this list is nearly complete. Two packages I maintain 
that would be affected (fmidi and giada) are absent from the list.


Using the following command:

    mock -r fedora-rawhide-x86_64 --dnf-cmd -- repoquery 
--whatrequires 'libfmt.so.8*'


I found these additional dependent packages that were missing from the 
original list:


  * bear
  * cachelib
  * easyeffects
  * easyrpg-player
  * fb303
  * fbthrift
  * fizz
  * fmidi
  * freeopcua
  * gerbera
  * giada
  * gnuradio
  * gr-funcube
  * libsemigroups
  * luxcorerender
  * mcrouter
  * nheko
  * proxygen
  * rstudio
  * wangle
  * watchman
  * waybar

I will go ahead and rebuild bear, fmidi, and giada into the side tag.

On 7/10/22 13:43, Vitaly Zaitsev via devel wrote:

Hello.

fmt 9.0.x update will include a soversion bump from .8 to .9. It has 
both API and ABI changes.


Changelog: https://github.com/fmtlib/fmt/releases/tag/9.0.0

The list of affected packages in Rawhide:
0ad
OpenImageIO
cantera
ceph
dolphin-emu
domoticz
folly
libsonata
mkvtoolnix
sdrpp
spdlog
vcpkg
zswap-cli

I can rebuild only spdlog, vcpkg and zswap-cli. For others, I will 
need proven-packagers assistance.


Please use the f37-build-side-54844 side tag. I will merge it into 
Rawhide later.




___
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


___
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


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: 

Re: F37 proposal: Add -fno-omit-frame-pointer to default compilation flags (System-Wide Change proposal)

[Daniel Alley]

> Unfortunately, no, there's no in-kernel DWARF unwinder due to the complexity 
> involved.
> Instead, the kernel uses ORC and has an unwinder for that. Adding ORC support 
> to all of
> Linux userspace so that we can unwind it in the kernel isn't likely to 
> happen, since
> all tooling would have to be changed to support ORC.

A huge task, most definitely.  Setting that aside though, which cases (if any) 
would that solution *not* handle?  Is the level of effort required the primary 
blocker to such a solution, or are there technical ones as well?
___
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

[Bug 2105286] Please branch and build perl-Net-SSH in epel8

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2105286

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #3 from Fedora Update System  ---
FEDORA-EPEL-2022-6ca7ca has been pushed to the Fedora EPEL 8 testing
repository.

You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-6ca7ca

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2105286
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2105287] Please branch and build perl-Net-SSH in epel9

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2105287

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #3 from Fedora Update System  ---
FEDORA-EPEL-2022-c43b1627b3 has been pushed to the Fedora EPEL 9 testing
repository.

You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-c43b1627b3

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2105287
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2102631] Add perl-Class-C3-Componentised to EPEL 9

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2102631

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #3 from Fedora Update System  ---
FEDORA-EPEL-2022-96ea163740 has been pushed to the Fedora EPEL 9 testing
repository.

You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-96ea163740

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2102631
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[EPEL-devel] Fedora EPEL 7 updates-testing report

[updates]

The following Fedora EPEL 7 Security updates need testing:
 Age  URL
   3  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-463787a597   
seamonkey-2.53.13-1.el7


The following builds have been pushed to Fedora EPEL 7 updates-testing

aha-0.5.1-2.el7

Details about builds:



 aha-0.5.1-2.el7 (FEDORA-EPEL-2022-c28798b354)
 Convert terminal output to HTML

Update Information:

Add a patch to fix segfault because of null pointer dereference

ChangeLog:

* Mon Jul 11 2022 Artur Frenszek-Iwicki  - 0.5.1-2
- Add a patch to fix segfault because of null pointer dereference


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

[Bug 2102687] Add perl-Text-RecordParser to EPEL 9

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2102687
Bug 2102687 depends on bug 2103432, which changed state.

Bug 2103432 Summary: Add perl-Text-TabularDisplay to EPEL 9
https://bugzilla.redhat.com/show_bug.cgi?id=2103432

   What|Removed |Added

 Status|ON_QA   |CLOSED
 Resolution|--- |ERRATA




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2102687
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2103432] Add perl-Text-TabularDisplay to EPEL 9

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2103432

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version||perl-Text-TabularDisplay-1.
   ||38-23.el9
 Status|ON_QA   |CLOSED
 Resolution|--- |ERRATA
Last Closed||2022-07-12 03:03:17



--- Comment #4 from Fedora Update System  ---
FEDORA-EPEL-2022-bf41796b31 has been pushed to the Fedora EPEL 9 stable
repository.
If problem still persists, please make note of it in this bug report.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2103432
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2102642] Add perl-Class-Trigger to EPEL 9

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2102642

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version||perl-Class-Trigger-0.15-3.e
   ||l9
 Resolution|--- |ERRATA
 Status|ON_QA   |CLOSED
Last Closed||2022-07-12 03:03:34



--- Comment #4 from Fedora Update System  ---
FEDORA-EPEL-2022-62304025c0 has been pushed to the Fedora EPEL 9 stable
repository.
If problem still persists, please make note of it in this bug report.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2102642
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2102597] Add perl-DBIx-Class to EPEL 9

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2102597
Bug 2102597 depends on bug 2102652, which changed state.

Bug 2102652 Summary: Add perl-MooseX-Types-JSON to EPEL 9
https://bugzilla.redhat.com/show_bug.cgi?id=2102652

   What|Removed |Added

 Status|ON_QA   |CLOSED
 Resolution|--- |ERRATA




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2102597
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2102597] Add perl-DBIx-Class to EPEL 9

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2102597
Bug 2102597 depends on bug 2102642, which changed state.

Bug 2102642 Summary: Add perl-Class-Trigger to EPEL 9
https://bugzilla.redhat.com/show_bug.cgi?id=2102642

   What|Removed |Added

 Status|ON_QA   |CLOSED
 Resolution|--- |ERRATA




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2102597
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2102597] Add perl-DBIx-Class to EPEL 9

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2102597
Bug 2102597 depends on bug 2102653, which changed state.

Bug 2102653 Summary: Add perl-MooseX-Types-LoadableClass to EPEL 9
https://bugzilla.redhat.com/show_bug.cgi?id=2102653

   What|Removed |Added

 Status|ON_QA   |CLOSED
 Resolution|--- |ERRATA




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2102597
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2102653] Add perl-MooseX-Types-LoadableClass to EPEL 9

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2102653

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version||perl-MooseX-Types-LoadableC
   ||lass-0.015-16.el9
 Status|ON_QA   |CLOSED
 Resolution|--- |ERRATA
Last Closed||2022-07-12 03:03:00



--- Comment #4 from Fedora Update System  ---
FEDORA-EPEL-2022-bf41796b31 has been pushed to the Fedora EPEL 9 stable
repository.
If problem still persists, please make note of it in this bug report.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2102653
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2102652] Add perl-MooseX-Types-JSON to EPEL 9

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2102652

Fedora Update System  changed:

   What|Removed |Added

 Resolution|--- |ERRATA
 Status|ON_QA   |CLOSED
   Fixed In Version||perl-MooseX-Types-JSON-1.01
   ||-2.el9
Last Closed||2022-07-12 03:02:43



--- Comment #4 from Fedora Update System  ---
FEDORA-EPEL-2022-bf41796b31 has been pushed to the Fedora EPEL 9 stable
repository.
If problem still persists, please make note of it in this bug report.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2102652
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2103378] perl-Socket-2.035 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2103378

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #2 from Fedora Update System  ---
FEDORA-2022-1a662f3bdc has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh
--advisory=FEDORA-2022-1a662f3bdc`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2022-1a662f3bdc

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2103378
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Python package review

[Maxwell G via devel]

On 22/07/12 12:28AM, chedi toueiti wrote:
> I'm looking for help review the following python packages needed by
> python-jsonschema+format
> 
> 
> python-rfc3339-validator:
> https://bugzilla.redhat.com/show_bug.cgi?id=2106174

@music already packaged this (I was the reviewer), but it seems he has
not yet built it for f35 and f36. Ben, can you please handle this?


-- 
Thanks,

Maxwell G (@gotmax23)
Pronouns: He/Him/His


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: Python package review

[Maxwell G via devel]

On 22/07/12 12:28AM, chedi toueiti wrote:
> I'm looking for help review the following python packages needed by
> python-jsonschema+format
> 
> 
> python-rfc3339-validator:
> https://bugzilla.redhat.com/show_bug.cgi?id=2106174

@music already packaged this (I was the reviewer), but it seems he has
not yet built it for f35 and f36. Ben, can you please handle this?


-- 
Thanks,

Maxwell G (@gotmax23)
Pronouns: He/Him/His


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

Python package review

[chedi toueiti]

Hi,


I'm looking for help review the following python packages needed by 
python-jsonschema+format



python-rfc3339-validator: 
https://bugzilla.redhat.com/show_bug.cgi?id=2106174


python-rfc3986-validator: 
https://bugzilla.redhat.com/show_bug.cgi?id=2106171



and let me know if you need something reviewed in exchange.


Regards,


___
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

rpmbuild is very slow with large files

[Marius Schwarz]

Hi,

I have just create(d/ not finished yet, started 15 minutes ago) a ~2.5 
GB rpm and found, that rpmbuild is an extrem bottleneck.


IMHO, this is caused by a fileread function which reads files in 32k 
blocks, which is very slow and extrem IO intensive.  The result is a 
task running at 1 core at 100% perma. With changes to larger chunks, we 
can speed up so many build tasks on the farm.


Multicore use would also be helpful i.e. while packing the files.

Any counter-arguments ?

strace example:

[pid 2604060] clock_gettime(CLOCK_REALTIME, {tv_sec=1657579222, 
tv_nsec=477601377}) = 0
[pid 2604060] clock_gettime(CLOCK_REALTIME, {tv_sec=1657579222, 
tv_nsec=477685727}) = 0
[pid 2604060] clock_gettime(CLOCK_REALTIME, {tv_sec=1657579222, 
tv_nsec=477892054}) = 0
[pid 2604060] clock_gettime(CLOCK_REALTIME, {tv_sec=1657579222, 
tv_nsec=47876}) = 0
[pid 2604060] read(5, "_I @_I s_I t_E\nauss\303\244het 
auss\303\244h"..., 32768) = 32768
[pid 2604060] clock_gettime(CLOCK_REALTIME, {tv_sec=1657579222, 
tv_nsec=478212651}) = 0
[pid 2604060] clock_gettime(CLOCK_REALTIME, {tv_sec=1657579222, 
tv_nsec=478301347}) = 0
[pid 2604060] clock_gettime(CLOCK_REALTIME, {tv_sec=1657579222, 
tv_nsec=478409015}) = 0
[pid 2604060] clock_gettime(CLOCK_REALTIME, {tv_sec=1657579222, 
tv_nsec=478505273}) = 0
[pid 2604060] clock_gettime(CLOCK_REALTIME, {tv_sec=1657579222, 
tv_nsec=478701366}) = 0
[pid 2604060] clock_gettime(CLOCK_REALTIME, {tv_sec=1657579222, 
tv_nsec=478784826}) = 0

[pid 2604060] read(5, " Y_I k_I t_E\naustun austun 'aU_B"..., 32768) = 32768
[pid 2604060] clock_gettime(CLOCK_REALTIME, {tv_sec=1657579222, 
tv_nsec=478962539}) = 0
[pid 2604060] clock_gettime(CLOCK_REALTIME, {tv_sec=1657579222, 
tv_nsec=479045029}) = 0
[pid 2604060] clock_gettime(CLOCK_REALTIME, {tv_sec=1657579222, 
tv_nsec=479130924}) = 0
[pid 2604060] clock_gettime(CLOCK_REALTIME, {tv_sec=1657579222, 
tv_nsec=479213446}) = 0
[pid 2604060] clock_gettime(CLOCK_REALTIME, {tv_sec=1657579222, 
tv_nsec=479407336}) = 0

[pid 2604060] clock_gettime(CLOCK_REAobjections
LTIME, {tv_sec=1657579222, tv_nsec=479489832}) = 0
[pid 2604060] read(5, "s_I v_I u:_I k_I s_I @_I s_E\naus"..., 32768) = 32768
[pid 2604060] clock_gettime(CLOCK_REALTIME, {tv_sec=1657579222, 
tv_nsec=479720335}) = 0
[pid 2604060] clock_gettime(CLOCK_REALTIME, {tv_sec=1657579222, 
tv_nsec=479803090}) = 0
[pid 2604060] clock_gettime(CLOCK_REALTIME, {tv_sec=1657579222, 
tv_nsec=479950309}) = 0
[pid 2604060] clock_gettime(CLOCK_REALTIME, {tv_sec=1657579222, 
tv_nsec=480067186}) = 0
[pid 2604060] clock_gettime(CLOCK_REALTIME, {tv_sec=1657579222, 
tv_nsec=480305924}) = 0
[pid 2604060] clock_gettime(CLOCK_REALTIME, {tv_sec=1657579222, 
tv_nsec=480417985}) = 0

[pid 2604060] read(5, "B s_I ts_I u:_I g_I R_I E_I n_I "..., 32768) = 32768
[pid 2604060] clock_gettime(CLOCK_REALTIME, {tv_sec=1657579222, 
tv_nsec=480654716}) = 0
[pid 2604060] clock_gettime(CLOCK_REALTIME, {tv_sec=1657579222, 
tv_nsec=480763606}) = 0


and I don't think, this tasks needs to read the clock that often too.
___
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: Once again, more than 8 days delayed notifications

[Demi Marie Obenour]

On 7/11/22 10:05, Stephen Smoogen wrote:
> On Mon, 11 Jul 2022 at 09:36, Petr Menšík  wrote:
> 
>> Do we have any notification alternative interface other than IRC? What
>> about pushing notifications to matrix, XMPP or other protocol/service?
>>
>> I think IRC has often also not-so-short delays. Is there something we
>> can to to improve the situation?
>>
>>
> At this point the code using FMN is getting rewritten and any additional
> notifications will need to be in that rewrite. That said, IRC is actually
> one of the fastest ones we can push to. Each additional service adds in
> slowdowns as the communication requires accounts, special routers, people
> who actually use those services to know how they work, and various other
> infrastructure with the only return being a ton of complaints when there is
> any problem in them.
> 
> Every person who uses notifications is an endpoint who has to be 'polled'
> by that notification, and there can be a lot of overhead in doing so even
> when people think of it as a fire-and-forget-bus. Every failed or slow or
> bad end-point slows down the entire system which grows over time. Email
> delivery problems from mailing lists are generally caused by the N hundred
> developers who decided they needed every notification as an email and have
> clogged up the outgoing queues because every mail system decides that a
> mass rebuild is a spam attack. The same goes with other systems (IRC, etc)
> where a large number of notifications do not look much different from a
> DOS.
> 
> While notifications is a great idea, it is also a hard problem. Please help
> the team who will be working on it.

In the case of email, is it possible to offload everything to a mail
server like Postfix?  That should be able to deal with a huge queue
without too many problems and without Fedora needing to write email
handling code.  Just send the email to the mail server and let the
mail server deal with delivery.

For other services, one option would be a language
(Erlang? Elixir?) designed for very high levels of concurrency and
reliability.  That might be a better choice than Python.
-- 
Sincerely,
Demi Marie Obenour (she/her/hers)
___
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

[Bug 2105286] Please branch and build perl-Net-SSH in epel8

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2105286

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



--- Comment #2 from Fedora Update System  ---
FEDORA-EPEL-2022-6ca7ca has been submitted as an update to Fedora EPEL 8.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-6ca7ca


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2105286
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2102631] Add perl-Class-C3-Componentised to EPEL 9

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2102631

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



--- Comment #2 from Fedora Update System  ---
FEDORA-EPEL-2022-96ea163740 has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-96ea163740


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2102631
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2105287] Please branch and build perl-Net-SSH in epel9

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2105287

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



--- Comment #2 from Fedora Update System  ---
FEDORA-EPEL-2022-c43b1627b3 has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-c43b1627b3


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2105287
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Python 3.11 final release might be delayed to December

[Miro Hrončok]

On 05. 07. 22 13:17, Miro Hrončok wrote:

Hello,
forwarding this  message to Fedora.

Will know more by the end of this week -- we might need to consider reverting 
back to Python 3.10 if we don't want to ship Fedora 37 GA with a beta version 
of Python :(


The fourth beta is out.

"As the requirements to continue with the regular schedule are met, we are 
going to still target the final release of Monday, 2022-10-03."


https://mail.python.org/archives/list/python-...@python.org/message/VD7YNBVMEPKZLRA6VOTYAQYTEZPDH6Q7/

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

Re: Python 3.11 final release might be delayed to December

[Miro Hrončok]

On 05. 07. 22 13:17, Miro Hrončok wrote:

Hello,
forwarding this  message to Fedora.

Will know more by the end of this week -- we might need to consider reverting 
back to Python 3.10 if we don't want to ship Fedora 37 GA with a beta version 
of Python :(


The fourth beta is out.

"As the requirements to continue with the regular schedule are met, we are 
going to still target the final release of Monday, 2022-10-03."


https://mail.python.org/archives/list/python-...@python.org/message/VD7YNBVMEPKZLRA6VOTYAQYTEZPDH6Q7/

--
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

Re: F37 proposal: Add -fno-omit-frame-pointer to default compilation flags (System-Wide Change proposal)

[Christian Hergert]

> My comment was specifically about sysprof.  I've been told that the
> GNOME developers will not even consider anything else.  This means that
> we need to fix sysprof.  If we do that, it will be possible to use GNOME
> OS for profiling on older CPUs, and hardware-assisted backtraces on
> newer CPUs on Fedora (at least Skylake and Zen 3, especially once we've
> got userspace SHSTK support).

As the maintainer of sysprof, trust me when I say that I'd be thrilled if GNOME 
used something else so it's one less thing to maintain. But the conjoining of 
data really is the value proposition which has kept it alive.

> * Enhance sysprof with LBR and SHSTK support.

Agreed that regardless of this proposal, I'd be happy to see support for 
addition data recording features in Sysprof. I've filed 
https://gitlab.gnome.org/GNOME/sysprof/-/issues/77 to track it and would 
appreciate any comments you can leave about how/what that would entail.
___
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

[Bug 2105729] pangzero and frozen-bubble won't launch and segfault on F36

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2105729



--- Comment #7 from Hans de Goede  ---
(In reply to Sergio Basto from comment #6)
> Hello,
> I just checked, I already got /usr/lib64/libXi.so.6 installed on F35 and F36
> so it segfault with libXi.so.6 installed

Can you collect a backtrace?

Run:

gdb /usr/bin/perl

answer "y" to the question about using debuginfod and then inside gfb do:

run /usr/bin/frozen-bubble

And then once it crashes type "bt" on the gdb prompt and copy and paste the
output here.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2105729
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Announcing fmt library soversion bump

[Ben Beasley]

Two of the three packages I tried to rebuild (bear and fmidi) failed 
with errors like:


/usr/include/fmt/core.h:1733:7: error: static assertion failed: Cannot format an 
argument. To make type T formattable provide a formatter 
specialization:https://fmt.dev/latest/api.html#udt
 1733 |   formattable,
  |   ^~~

Links to failing scratch builds in the side tag:

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

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

I found that there was already a bug report open upstream for Bear: 
https://github.com/rizsotto/Bear/issues/471


If that FTBFS rate is typical of the full set of affected packages, then 
merging the side tag without resolving the API incompatibilities in 
dependent packages will be pretty disruptive to Rawhide as a whole.


Would you consider setting up a COPR to figure out how many packages are 
affected by the API changes, and filing Bugzillas on the affected 
dependent packages? It might take a while for affected package 
maintainers to become aware of the problem, investigate, and perhaps 
work with upstreams to prepare the necessary patches.


Link to fmt 9.0.0 release notes: 
https://github.com/fmtlib/fmt/releases/tag/9.0.0


– Ben

On 7/11/22 12:21, Ben Beasley wrote:


I don’t believe this list is nearly complete. Two packages I maintain 
that would be affected (fmidi and giada) are absent from the list.


Using the following command:

    mock -r fedora-rawhide-x86_64 --dnf-cmd -- repoquery 
--whatrequires 'libfmt.so.8*'


I found these additional dependent packages that were missing from the 
original list:


  * bear
  * cachelib
  * easyeffects
  * easyrpg-player
  * fb303
  * fbthrift
  * fizz
  * fmidi
  * freeopcua
  * gerbera
  * giada
  * gnuradio
  * gr-funcube
  * libsemigroups
  * luxcorerender
  * mcrouter
  * nheko
  * proxygen
  * rstudio
  * wangle
  * watchman
  * waybar

I will go ahead and rebuild bear, fmidi, and giada into the side tag.

On 7/10/22 13:43, Vitaly Zaitsev via devel wrote:

Hello.

fmt 9.0.x update will include a soversion bump from .8 to .9. It has 
both API and ABI changes.


Changelog: https://github.com/fmtlib/fmt/releases/tag/9.0.0

The list of affected packages in Rawhide:
0ad
OpenImageIO
cantera
ceph
dolphin-emu
domoticz
folly
libsonata
mkvtoolnix
sdrpp
spdlog
vcpkg
zswap-cli

I can rebuild only spdlog, vcpkg and zswap-cli. For others, I will 
need proven-packagers assistance.


Please use the f37-build-side-54844 side tag. I will merge it into 
Rawhide later.




___
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___
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: F37 proposal: Stratis 3.1.0 (Self-Contained change)

[Ben Cotton]

Note that the owners have submitted an updated proposal for Stratis
3.2.0: https://fedoraproject.org/wiki/Changes/Stratis_3.2.0

Since this is a leaf package and the differences between 3.1 and 3.2
do not seem significant to our process, I will restart the clock on
the FESCo vote for the updated proposal instead of starting the whole
process over. See https://pagure.io/fesco/issue/2822


-- 
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
___
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-20220711.n.0 compose check report

[Fedora compose checker]

Missing expected images:

Minimal raw-xz armhfp

Compose FAILS proposed Rawhide gating check!
2 of 43 required tests failed
openQA tests matching unsatisfied gating requirements shown with **GATING** 
below

Failed openQA tests: 13/236 (x86_64), 14/165 (aarch64)

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

ID: 1321047 Test: x86_64 Everything-boot-iso install_default@uefi **GATING**
URL: https://openqa.fedoraproject.org/tests/1321047
ID: 1321077 Test: x86_64 KDE-live-iso install_no_user **GATING**
URL: https://openqa.fedoraproject.org/tests/1321077
ID: 1321136 Test: aarch64 Server-dvd-iso install_btrfs_preserve_home@uefi
URL: https://openqa.fedoraproject.org/tests/1321136
ID: 1321151 Test: aarch64 Server-dvd-iso 
install_blivet_btrfs_preserve_home_uefi@uefi
URL: https://openqa.fedoraproject.org/tests/1321151
ID: 1321177 Test: aarch64 Server-dvd-iso install_vncconnect_server@uefi
URL: https://openqa.fedoraproject.org/tests/1321177
ID: 1321202 Test: aarch64 Workstation-raw_xz-raw.xz clocks@uefi
URL: https://openqa.fedoraproject.org/tests/1321202
ID: 1321208 Test: aarch64 Workstation-raw_xz-raw.xz help_viewer@uefi
URL: https://openqa.fedoraproject.org/tests/1321208
ID: 1321252 Test: aarch64 Workstation-upgrade evince@uefi
URL: https://openqa.fedoraproject.org/tests/1321252
ID: 1321259 Test: aarch64 Workstation-upgrade desktop_printing_builtin@uefi
URL: https://openqa.fedoraproject.org/tests/1321259
ID: 1321264 Test: x86_64 universal install_asian_language
URL: https://openqa.fedoraproject.org/tests/1321264

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

ID: 1321061 Test: x86_64 Workstation-live-iso apps_startstop
URL: https://openqa.fedoraproject.org/tests/1321061
ID: 1321084 Test: x86_64 KDE-live-iso desktop_login
URL: https://openqa.fedoraproject.org/tests/1321084
ID: 1321090 Test: x86_64 KDE-live-iso apps_startstop
URL: https://openqa.fedoraproject.org/tests/1321090
ID: 1321103 Test: x86_64 Silverblue-dvd_ostree-iso gnome_text_editor
URL: https://openqa.fedoraproject.org/tests/1321103
ID: 1321109 Test: x86_64 Silverblue-dvd_ostree-iso evince
URL: https://openqa.fedoraproject.org/tests/1321109
ID: 132 Test: x86_64 Silverblue-dvd_ostree-iso eog
URL: https://openqa.fedoraproject.org/tests/132
ID: 1321137 Test: aarch64 Server-dvd-iso 
install_btrfs_preserve_home_uefi@uefi
URL: https://openqa.fedoraproject.org/tests/1321137
ID: 1321175 Test: aarch64 Server-dvd-iso server_cockpit_basic@uefi
URL: https://openqa.fedoraproject.org/tests/1321175
ID: 1321209 Test: aarch64 Workstation-raw_xz-raw.xz gnome_text_editor@uefi
URL: https://openqa.fedoraproject.org/tests/1321209
ID: 1321221 Test: x86_64 Workstation-upgrade apps_startstop
URL: https://openqa.fedoraproject.org/tests/1321221
ID: 1321230 Test: x86_64 Workstation-upgrade desktop_fprint
URL: https://openqa.fedoraproject.org/tests/1321230
ID: 1321235 Test: x86_64 Workstation-upgrade desktop_login
URL: https://openqa.fedoraproject.org/tests/1321235
ID: 1321260 Test: aarch64 Workstation-upgrade help_viewer@uefi
URL: https://openqa.fedoraproject.org/tests/1321260
ID: 1321261 Test: aarch64 Workstation-upgrade gnome_text_editor@uefi
URL: https://openqa.fedoraproject.org/tests/1321261
ID: 1321295 Test: x86_64 universal install_arabic_language
URL: https://openqa.fedoraproject.org/tests/1321295
ID: 1321359 Test: aarch64 universal install_arabic_language@uefi
URL: https://openqa.fedoraproject.org/tests/1321359
ID: 1321452 Test: aarch64 universal install_asian_language@uefi
URL: https://openqa.fedoraproject.org/tests/1321452

Soft failed openQA tests: 6/236 (x86_64), 5/165 (aarch64)
(Tests completed, but using a workaround for a known bug)

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

ID: 1321072 Test: x86_64 Workstation-live-iso eog
URL: https://openqa.fedoraproject.org/tests/1321072
ID: 1321110 Test: x86_64 Silverblue-dvd_ostree-iso clocks
URL: https://openqa.fedoraproject.org/tests/1321110
ID: 1321113 Test: x86_64 Silverblue-dvd_ostree-iso desktop_browser
URL: https://openqa.fedoraproject.org/tests/1321113
ID: 1321124 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi
URL: https://openqa.fedoraproject.org/tests/1321124
ID: 1321203 Test: aarch64 Workstation-raw_xz-raw.xz eog@uefi
URL: https://openqa.fedoraproject.org/tests/1321203
ID: 1321219 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi
URL: https://openqa.fedoraproject.org/tests/1321219
ID: 1321254 Test: aarch64 Workstation-upgrade eog@uefi
URL: https://openqa.fedoraproject.org/tests/1321254
ID: 1321270 Test: x86_64 universal upgrade_server_domain_controller
URL: https://openqa.fedoraproject.org/tests/1321270
ID: 1321306 Test: x86_64 universal upgrade_2_server_domain_controller
URL: https://openqa.fedoraproject.org/tests/1321306
ID: 1321342 Test: aarch64 universal 

[EPEL-devel] Looking for a fedora review of an epel7-only new package

[Dave Dykstra via epel-devel]

I asked for a review swap on this on fedora-devel but so far did not
get any takers.  I'm thinking maybe a lot of Fedora people don't care
that much about an epel7-only package.  The package is fuse2fs and
this is the request:
https://bugzilla.redhat.com/show_bug.cgi?id=2104533

The tool is standard in the e2fsprogs package on el8 and later, but I
need to use it from apptainer on el7 and later, thus the desire to
install it as its own package in epel7.  I am hoping to use this in an
apptainer release candidate in just a couple of weeks, so it would be
very good to have a timely review and approval.

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

Re: Announcing fmt library soversion bump

[Ben Beasley]

I don’t believe this list is nearly complete. Two packages I maintain 
that would be affected (fmidi and giada) are absent from the list.


Using the following command:

    mock -r fedora-rawhide-x86_64 --dnf-cmd -- repoquery --whatrequires 
'libfmt.so.8*'


I found these additional dependent packages that were missing from the 
original list:


 * bear
 * cachelib
 * easyeffects
 * easyrpg-player
 * fb303
 * fbthrift
 * fizz
 * fmidi
 * freeopcua
 * gerbera
 * giada
 * gnuradio
 * gr-funcube
 * libsemigroups
 * luxcorerender
 * mcrouter
 * nheko
 * proxygen
 * rstudio
 * wangle
 * watchman
 * waybar

I will go ahead and rebuild bear, fmidi, and giada into the side tag.

On 7/10/22 13:43, Vitaly Zaitsev via devel wrote:

Hello.

fmt 9.0.x update will include a soversion bump from .8 to .9. It has 
both API and ABI changes.


Changelog: https://github.com/fmtlib/fmt/releases/tag/9.0.0

The list of affected packages in Rawhide:
0ad
OpenImageIO
cantera
ceph
dolphin-emu
domoticz
folly
libsonata
mkvtoolnix
sdrpp
spdlog
vcpkg
zswap-cli

I can rebuild only spdlog, vcpkg and zswap-cli. For others, I will 
need proven-packagers assistance.


Please use the f37-build-side-54844 side tag. I will merge it into 
Rawhide later.
___
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: F37 proposal: Officially Support Raspberry Pi 4 (Self-Contained Change proposal)

[Adam Williamson]

On Tue, 2022-07-05 at 17:16 -0400, Ben Cotton wrote:
> == Scope ==
> * Proposal owners:
> ** Ensure any patches required are accepted upstream
> ** Work with kernel, mesa and other maintainers to ensure everything
> is as it should be
> ** Test

Also, 'add it to the list of officially-supported platforms'. Which
begs the question, 'which one?' I noticed last week there are (at
least) two:

https://fedoraproject.org/wiki/Architectures/ARM#Supported_Hardware_and_Devices
https://fedoraproject.org/wiki/Architectures/ARM/Supported_Platforms

can that be cut down to one and the winner updated?

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: Once again, more than 8 days delayed notifications

[Tomasz Torcz]

On Mon, Jul 11, 2022 at 03:36:08PM +0200, Petr Menšík wrote:
> Do we have any notification alternative interface other than IRC? What about
> pushing notifications to matrix, XMPP or other protocol/service?

  There were other channels like email, but they do not work, too.
I seem to recevive last notification by email in the middle of November 2021.

-- 
Tomasz TorczOnly gods can safely risk perfection,
to...@pipebreaker.pl it's a dangerous thing for a man.  — Alia
___
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

[Bug 2105729] pangzero and frozen-bubble won't launch and segfault on F36

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2105729



--- Comment #6 from Sergio Basto  ---
Hello,
I just checked, I already got /usr/lib64/libXi.so.6 installed on F35 and F36 so
it segfault with libXi.so.6 installed


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2105729
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2105729] pangzero and frozen-bubble won't launch and segfault on F36

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2105729



--- Comment #5 from Hans de Goede  ---
Created attachment 1896084
  --> https://bugzilla.redhat.com/attachment.cgi?id=1896084=edit
PATCH to fix crash on systems where libXi.so.6 is not installed

This SDL2 patch fixes things for me in the libXi.so.6 missing case.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2105729
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2105729] pangzero and frozen-bubble won't launch and segfault on F36

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2105729



--- Comment #4 from Hans de Goede  ---
Note that on Fedora Workstation gnome-shell brings in libXi so I guess that you
are both using a different spin ?


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2105729
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2105729] pangzero and frozen-bubble won't launch and segfault on F36

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2105729



--- Comment #3 from Hans de Goede  ---
The problem of the posted backtrace is that /usr/lib64/libXi.so.6 is not there
and SDL2 dlopen()'s everything...

Arguably this is a bug in the posted SDL2 code snippet since it does not do a
runtime check for
the global "int SDL_X11_HAVE_XINPUT2" variable.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2105729
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2105631] perl-Imager-1.019 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2105631

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|ASSIGNED|CLOSED
   Fixed In Version||perl-Imager-1.019-1.fc37
 Resolution|--- |RAWHIDE
Last Closed||2022-07-11 14:15:14




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2105631
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Once again, more than 8 days delayed notifications

[Stephen Smoogen]

On Mon, 11 Jul 2022 at 09:36, Petr Menšík  wrote:

> Do we have any notification alternative interface other than IRC? What
> about pushing notifications to matrix, XMPP or other protocol/service?
>
> I think IRC has often also not-so-short delays. Is there something we
> can to to improve the situation?
>
>
At this point the code using FMN is getting rewritten and any additional
notifications will need to be in that rewrite. That said, IRC is actually
one of the fastest ones we can push to. Each additional service adds in
slowdowns as the communication requires accounts, special routers, people
who actually use those services to know how they work, and various other
infrastructure with the only return being a ton of complaints when there is
any problem in them.

Every person who uses notifications is an endpoint who has to be 'polled'
by that notification, and there can be a lot of overhead in doing so even
when people think of it as a fire-and-forget-bus. Every failed or slow or
bad end-point slows down the entire system which grows over time. Email
delivery problems from mailing lists are generally caused by the N hundred
developers who decided they needed every notification as an email and have
clogged up the outgoing queues because every mail system decides that a
mass rebuild is a spam attack. The same goes with other systems (IRC, etc)
where a large number of notifications do not look much different from a
DOS.

While notifications is a great idea, it is also a hard problem. Please help
the team who will be working on it.



-- 
Stephen Smoogen, Red Hat Automotive
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

[Bug 2105631] perl-Imager-1.019 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2105631

Jitka Plesnikova  changed:

   What|Removed |Added

   Doc Type|--- |If docs needed, set a value
 Status|NEW |ASSIGNED
 CC|jples...@redhat.com,|
   |st...@silug.org |




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2105631
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: proposal idea: EOL notifications

[Kate Stewart]

On Mon, Jul 11, 2022 at 6:02 AM Josh Boyer 
wrote:

> On Sun, Jul 10, 2022 at 12:34 PM Miroslav Suchý  wrote:
> >
> > Dne 08. 07. 22 v 4:59 Stewart Smith via devel napsal(a):
> >
> > Another - what do we do about, e.g., Fedora IoT and Fedora CoreOS,
> > which have their own somewhat different release/life cycles? What about
> > module lifecycles? What is it about *lifecycles* that's important,
> > anyway? Don't we maybe want to just have a sort of generic system for
> > "important events"?
> >
> > I view it as a mechanism to communicate well in advance of when someone
> > is going to have to do work.
> >
> > Fedora is the simple case: every 6-12 months you're going to have to
> > upgrade the version of the OS.
> >
> > And when implementing this for Fedora, can you bear RHEL in mind too?
> Because it has several levels of EOL
> >
> >
> https://endoflife.software/operating-systems/linux/red-hat-enterprise-linux-rhel
>
> RHEL is already implementing it's own scheme for lifecycle metadata.
>

A "ValidUntilDate" was added to SPDX 2.3 about a month ago, to enable
capture of End of Support / End of Life information as metadata captured
about a package or group of packages, so different policies can be
articulated this way.   (see: https://github.com/spdx/spdx-spec/pull/709).
 In 2.3, it's an optional field, so if the information is available,
there's a place to put it.   Similarly a ReleaseDate and BuiltDate were
added, which are useful in some policy and automated checkers.

So for all systems generating SBOMs, there will be a standard place in the
SPDX metadata.  We're in the release candidate review for the 2.3
specification,  so if people see issues with the proposed syntax, comments
welcome at https://github.com/spdx/spdx-spec/issues.

Thanks,
Kate
___
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

[rpms/perl-Devel-FindPerl] PR #1: 0.016 bump

[Michal Josef Špaček]

mspacek merged a pull-request against the project: `perl-Devel-FindPerl` that 
you are following.

Merged pull-request:

``
0.016 bump
``

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

Re: Once again, more than 8 days delayed notifications

[Petr Menšík]

Do we have any notification alternative interface other than IRC? What 
about pushing notifications to matrix, XMPP or other protocol/service?


I think IRC has often also not-so-short delays. Is there something we 
can to to improve the situation?


On 09. 07. 22 15:24, Ralf Corsépius wrote:

Hi,

I thought the notification delay mess was fixed. Apparently, I was wrong.


I just received this:


Subject: corsepiu pushed 1 commit to rpms/perl-Sub-HandlesVia (rawhide)
Date: Sat,  9 Jul 2022 10:39:46 + (GMT)
From: notificati...@fedoraproject.org
...
Notification time stamped 2022-07-01 05:57:40 UTC
...



Ralf
___
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


--
Petr Menšík
Software Engineer, RHEL
Red Hat, http://www.redhat.com/
PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB
___
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

[rpms/perl-Devel-FindPerl] PR #1: 0.016 bump

[Michal Josef Špaček]

mspacek opened a new pull-request against the project: `perl-Devel-FindPerl` 
that you are following:
``
0.016 bump
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Devel-FindPerl/pull-request/1
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2103762] perl-Sys-Virt-8.5.0 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2103762



--- Comment #1 from Jitka Plesnikova  ---
It requires libvirt-8.5.0.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2103762
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Fedora rawhide compose report: 20220711.n.0 changes

[Fedora Rawhide Report]

OLD: Fedora-Rawhide-20220710.n.0
NEW: Fedora-Rawhide-20220711.n.0

= SUMMARY =
Added images:1
Dropped images:  0
Added packages:  12
Dropped packages:0
Upgraded packages:   61
Downgraded packages: 0

Size of added packages:  1.44 MiB
Size of dropped packages:0 B
Size of upgraded packages:   1.36 GiB
Size of downgraded packages: 0 B

Size change of upgraded packages:   -1.32 MiB
Size change of downgraded packages: 0 B

= ADDED IMAGES =
Image: Comp_Neuro live x86_64
Path: Labs/x86_64/iso/Fedora-Comp_Neuro-Live-x86_64-Rawhide-20220711.n.0.iso

= DROPPED IMAGES =

= ADDED PACKAGES =
Package: python-token-bucket-0.3.0-1.fc37
Summary: A Token Bucket implementation
RPMs:python3-token-bucket
Size:19.22 KiB

Package: rust-aparato-6.0.2-1.fc37
Summary: Pci.ids-compliant library for getting information about available PCI 
devices
RPMs:rust-aparato+default-devel rust-aparato-devel
Size:24.62 KiB

Package: rust-const_format_proc_macros-0.2.22-1.fc37
Summary: Implementation detail of the `const_format` crate
RPMs:rust-const_format_proc_macros+all-devel 
rust-const_format_proc_macros+debug-devel 
rust-const_format_proc_macros+default-devel 
rust-const_format_proc_macros+derive-devel 
rust-const_format_proc_macros+syn-devel rust-const_format_proc_macros-devel
Size:70.65 KiB

Package: rust-daemonize-0.4.1-2.fc37
Summary: Library to enable your code run as a daemon process on Unix-like 
systems
RPMs:rust-daemonize+default-devel rust-daemonize-devel
Size:29.41 KiB

Package: rust-gmp-mpfr-sys-1.4.8-1.fc37
Summary: Rust FFI bindings for GMP, MPFR and MPC
RPMs:rust-gmp-mpfr-sys+c-no-tests-devel rust-gmp-mpfr-sys+cnodelete-devel 
rust-gmp-mpfr-sys+default-devel rust-gmp-mpfr-sys+fail-on-warnings-devel 
rust-gmp-mpfr-sys+force-cross-devel rust-gmp-mpfr-sys+mpc-devel 
rust-gmp-mpfr-sys+mpfr-devel rust-gmp-mpfr-sys+use-system-libs-devel 
rust-gmp-mpfr-sys-devel
Size:323.12 KiB

Package: rust-impls-1.0.3-1.fc37
Summary: Determine if a type implements a logical trait expression
RPMs:rust-impls+default-devel rust-impls-devel
Size:27.79 KiB

Package: rust-local-encoding-0.2.0-1.fc37
Summary: Rust library for encoding/decoding a string with local charset
RPMs:rust-local-encoding+default-devel rust-local-encoding-devel
Size:20.94 KiB

Package: rust-local_ipaddress-0.1.3-1.fc37
Summary: Get your local IP address without panic
RPMs:local_ipaddress rust-local_ipaddress+default-devel 
rust-local_ipaddress-devel
Size:756.13 KiB

Package: rust-stfu8-0.2.5-1.fc37
Summary: Sorta Text Format in UTF-8
RPMs:rust-stfu8+default-devel rust-stfu8+testing-devel rust-stfu8-devel
Size:49.92 KiB

Package: rust-tokio-compat-0.1.6-1.fc37
Summary: Compatibility between tokio 0.2 and legacy versions
RPMs:rust-tokio-compat+blocking-devel rust-tokio-compat+default-devel 
rust-tokio-compat+pin-project-lite-devel 
rust-tokio-compat+rt-current-thread-devel rust-tokio-compat+rt-full-devel 
rust-tokio-compat+sink-devel rust-tokio-compat+tokio-current-thread-01-devel 
rust-tokio-compat+tokio-executor-01-devel 
rust-tokio-compat+tokio-reactor-01-devel rust-tokio-compat+tokio-timer-02-devel 
rust-tokio-compat-devel
Size:102.29 KiB

Package: rust-typed-builder-0.10.0-1.fc37
Summary: Compile-time type-checked builder derive
RPMs:rust-typed-builder+default-devel rust-typed-builder-devel
Size:37.51 KiB

Package: rust-uucore_procs-0.0.14-1.fc37
Summary: Uutils ~ 'uucore' proc-macros
RPMs:rust-uucore_procs+default-devel rust-uucore_procs-devel
Size:16.95 KiB


= DROPPED PACKAGES =

= UPGRADED PACKAGES =
Package:  airinv-1.00.7-1.fc37
Old package:  airinv-1.00.5-7.fc37
Summary:  C++ Simulated Airline Inventory Management System library
RPMs: airinv airinv-devel airinv-doc
Size: 3.48 MiB
Size change:  7.99 KiB
Changelog:
  * Wed May 04 2022 Thomas Rodgers  1.00.5-9
  - Rebuilt for Boost 1.78

  * Sun Jul 10 2022 Denis Arnaud  1.00.7-1
  - Upgraded to v1.00.7


Package:  airrac-1.00.6-1.fc37
Old package:  airrac-1.00.4-11.fc37
Summary:  C++ Simulated Revenue Accounting (RAC) System Library
RPMs: airrac airrac-devel airrac-doc
Size: 1.16 MiB
Size change:  1.33 KiB
Changelog:
  * Wed May 04 2022 Thomas Rodgers  1.00.4-15
  - Rebuilt for Boost 1.78

  * Sun Jul 10 2022 Denis Arnaud  1.00.6-1
  - Upgraded to v1.00.6


Package:  airtsp-1.01.9-1.fc37
Old package:  airtsp-1.01.8-5.fc37
Summary:  C++ Simulated Airline Travel Solution Provider Library
RPMs: airtsp airtsp-devel airtsp-doc
Size: 2.29 MiB
Size change:  5.06 KiB
Changelog:
  * Wed May 04 2022 Thomas Rodgers  1.01.8-8
  - Rebuilt for Boost 1.78

  * Sun Jul 10 2022 Denis Arnaud  1.01.9-1
  - Upgraded to v1.01.9


Package:  aml-0.2.2-1.fc37
Old package:  aml-0.2.0-4.fc36
Summary:  Another Main Loop
RPMs: aml aml-devel
Size: 151.30 KiB
Size change:  573 B

[Bug 2103484] perl-PAR-Packer-1.055 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2103484

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|ASSIGNED|CLOSED
 Resolution|--- |RAWHIDE
   Fixed In Version||perl-PAR-Packer-1.055-1.fc3
   ||7
Last Closed||2022-07-11 11:27:34




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2103484
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2103762] perl-Sys-Virt-8.5.0 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2103762

Jitka Plesnikova  changed:

   What|Removed |Added

   Doc Type|--- |If docs needed, set a value
 Status|NEW |ASSIGNED
 CC|berra...@redhat.com,|
   |crobi...@redhat.com,|
   |jples...@redhat.com,|
   |st...@silug.org |




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2103762
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: About Fedora containers

[Petr Hracek]

Hi Alejandro,

we have developed an easy GitHub Action [1].
The example how to use it is already mentioned in README.md [2].
All our images are automatically by merging PR pushed into Quay.io.
See an examples GitHub Action here [3].
As you can see the nginx-container image is automatically pushed to Quay.io
when the PR is merged or regularly each Wednesday.


[1] https://github.com/sclorg/build-and-push-action/
[2] https://github.com/sclorg/build-and-push-action/blob/main/README.md
[3] 
https://github.com/sclorg/nginx-container/blob/master/.github/workflows/build-and-push.yml


On 17.06.2022 15:59, Alejandro Saez Morollon wrote:

Hi all!

TL;DR: Is there any documentation about how to properly take care of
our containers? :)

---
The Go container has been outdated for a while, and I would love to
update it[0], but I'm not familiar with the container process in
Fedora.

I checked Python3's container[1] looking for information, and I saw
that the rawhide branch is not used in the same way we use it with the
RPMs.
Also, I saw that the s2i-base image is only available until F35. No
F36 or Rawhide.
And, it looks like they are only available for x86_64 platforms.

So I guess the main big question is: is there any documentation or
proposals I should be aware of? Is the Go container relevant?

cc'ed Container SIG's mailing list; I didn't see movement in the
mailing list, just in case.

[0] https://src.fedoraproject.org/container/golang
[1] https://src.fedoraproject.org/container/python3


Thank you very much!
___
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: Once again, more than 8 days delayed notifications

[Stephen Smoogen]

On Mon, 11 Jul 2022 at 06:22, Sérgio Basto  wrote:

> On Mon, 2022-07-11 at 09:35 +0200, Pierre-Yves Chibon wrote:
> > On Sat, Jul 09, 2022 at 09:36:14AM -0400, Stephen Smoogen wrote:
> > > On Sat, 9 Jul 2022 at 09:25, Ralf Corsépius 
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > I thought the notification delay mess was fixed. Apparently, I
> > > > was wrong.
> > > >
> > > >
> > >
> > > No, I believe the service which is behind these emails is called
> > > FMN. It is
> > > very fragile for multiple reasons where it falls over for different
> > > reasons
> > > all the time. It is the reason why it is on the top of being
> > > replaced by
> > > CPE in this quarter (aka by October-ish).
> >
> > Just a quick note, I doubt the app will be re-written and deploy in a
> > single
> > quarter, I expect this to be more a multi-months effort. So while it
> > has the top
> > of the priority list for CPE to work on, it'll still take a little
> > time before
> > we see a v4 (we've already restructured it 3 times).
> >
>
> I think you should disable the service or allocate someone to do
> something that mitigate the problem or reboot the service every time it
> stops
>
>
Like many services in Fedora, it is intertwined with other tools with a
bunch of duct tape and bailing wire that was going to be fixed when things
slowed down. You can't just disable it because then you cause other items
inside and outside of Fedora to break. You can't just reboot it because the
problem is usually some other service which is causing the holdup.

There are days when I regret leaving Fedora Infrastructure, but it is email
threads like this which remind me why I needed to.

-- 
Stephen Smoogen, Red Hat Automotive
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: proposal idea: EOL notifications

[Josh Boyer]

On Sun, Jul 10, 2022 at 12:34 PM Miroslav Suchý  wrote:
>
> Dne 08. 07. 22 v 4:59 Stewart Smith via devel napsal(a):
>
> Another - what do we do about, e.g., Fedora IoT and Fedora CoreOS,
> which have their own somewhat different release/life cycles? What about
> module lifecycles? What is it about *lifecycles* that's important,
> anyway? Don't we maybe want to just have a sort of generic system for
> "important events"?
>
> I view it as a mechanism to communicate well in advance of when someone
> is going to have to do work.
>
> Fedora is the simple case: every 6-12 months you're going to have to
> upgrade the version of the OS.
>
> And when implementing this for Fedora, can you bear RHEL in mind too? Because 
> it has several levels of EOL
>
> https://endoflife.software/operating-systems/linux/red-hat-enterprise-linux-rhel

RHEL is already implementing it's own scheme for lifecycle metadata.

josh
___
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

[Bug 2105729] pangzero and frozen-bubble won't launch and segfault on F36

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2105729

Petr Pisar  changed:

   What|Removed |Added

 CC||ppi...@redhat.com



--- Comment #2 from Petr Pisar  ---
frozen-bubble in F37 connected to X11 in F35:

(gdb) bt
#0  0x in  ()
#1  0x77486c0e in X11_Xinput2UngrabTouch (window=0x56c2dd10,
_this=) at
/usr/src/debug/SDL2-2.0.22-2.fc37.x86_64/src/video/x11/SDL_x11xinput2.c:385
#2  X11_SetWindowMouseGrab (_this=, window=0x56c2dd10,
grabbed=) at
/usr/src/debug/SDL2-2.0.22-2.fc37.x86_64/src/video/x11/SDL_x11window.c:1799
#3  0x77454d3f in SDL_UpdateWindowGrab (window=0x56c2dd10) at
/usr/src/debug/SDL2-2.0.22-2.fc37.x86_64/src/video/SDL_video.c:2816
#4  0x774bdd7c in SDL_OnWindowFocusGained (window=0x56c2dd10) at
/usr/src/debug/SDL2-2.0.22-2.fc37.x86_64/src/video/SDL_video.c:3031
#5  SDL_SendWindowEvent.isra.0 (window=window@entry=0x56c2dd10,
windowevent=windowevent@entry=12 '\f', data1=data1@entry=0,
data2=data2@entry=0)
at
/usr/src/debug/SDL2-2.0.22-2.fc37.x86_64/src/events/SDL_windowevents.c:168
#6  0x773cfb86 in SDL_SetKeyboardFocus (window=0x56c2dd10) at
/usr/src/debug/SDL2-2.0.22-2.fc37.x86_64/src/events/SDL_keyboard.c:660
#7  0x774770c4 in X11_DispatchFocusIn (_this=0x56bc8e50,
data=0x56c3eec0) at
/usr/src/debug/SDL2-2.0.22-2.fc37.x86_64/src/video/x11/SDL_x11events.c:440
#8  0x7747c46b in X11_DispatchEvent (_this=_this@entry=0x56bc8e50,
xevent=xevent@entry=0x7fffdca0) at
/usr/src/debug/SDL2-2.0.22-2.fc37.x86_64/src/video/x11/SDL_x11events.c:962
#9  0x7747d99b in X11_PumpEvents (_this=0x56bc8e50) at
/usr/src/debug/SDL2-2.0.22-2.fc37.x86_64/src/video/x11/SDL_x11events.c:1694
#10 0x773cf149 in SDL_PumpEventsInternal
(push_sentinel=push_sentinel@entry=SDL_TRUE) at
/usr/src/debug/SDL2-2.0.22-2.fc37.x86_64/src/events/SDL_events.c:847
#11 0x773cf44f in SDL_WaitEventTimeout_REAL (event=0x7fffdeb0,
timeout=0) at
/usr/src/debug/SDL2-2.0.22-2.fc37.x86_64/src/events/SDL_events.c:1024
#12 0x775464a1 in SDL_PumpEvents () at
/usr/src/debug/sdl12-compat-1.2.52-1.fc37.x86_64/src/SDL12_compat.c:5898
#13 0x7757181e in XS_SDL__Events_pump_events (my_perl=,
cv=0x56083830) at lib/SDL/Events.xs:60
#14 0x77d1eed0 in Perl_pp_entersub (my_perl=0x92a0) at
/usr/src/debug/perl-5.36.0-488.fc37.x86_64/pp_hot.c:5352
#15 0x77d10850 in Perl_runops_standard (my_perl=0x92a0) at
/usr/src/debug/perl-5.36.0-488.fc37.x86_64/run.c:41
#16 0x77c80eae in S_run_body (oldscope=,
my_perl=) at
/usr/src/debug/perl-5.36.0-488.fc37.x86_64/perl.c:2716
#17 perl_run (my_perl=0x92a0) at
/usr/src/debug/perl-5.36.0-488.fc37.x86_64/perl.c:2644
#18 0x534a in main (argc=, argv=,
env=) at
/usr/src/debug/perl-5.36.0-488.fc37.x86_64/perlmain.c:110

Frame #1 calls X11_XIUngrabTouchBegin():

void
X11_Xinput2UngrabTouch(_THIS, SDL_Window *window)
{
#if SDL_VIDEO_DRIVER_X11_XINPUT2_SUPPORTS_MULTITOUCH
SDL_WindowData *data = (SDL_WindowData *) window->driverdata;
Display *display = data->videodata->display;

XIGrabModifiers mods;

mods.modifiers = XIAnyModifier;
mods.status = 0;

→   X11_XIUngrabTouchBegin(display, XIAllDevices, data->xwindow, 1, );
#endif
}

(gdb) info locals 
data = 
display = 
mods = {modifiers = -2147483648, status = 0}

I will try to minimize the the reproducer.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2105729
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2105955] New: Upgrade perl-Type-Tiny to 1.014000

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2105955

Bug ID: 2105955
   Summary: Upgrade perl-Type-Tiny to 1.014000
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Type-Tiny
  Assignee: rc040...@freenet.de
  Reporter: jples...@redhat.com
QA Contact: extras...@fedoraproject.org
CC: p...@city-fan.org, perl-devel@lists.fedoraproject.org,
ppi...@redhat.com, rc040...@freenet.de,
xav...@bachelot.org
  Target Milestone: ---
Classification: Fedora



Latest Fedora delivers 1.012005 version. Upstream released 1.014000. When you
have free time, please upgrade it.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2105955
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2105954] New: Upgrade perl-Lingua-EN-Sentence to 0.33

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2105954

Bug ID: 2105954
   Summary: Upgrade perl-Lingua-EN-Sentence to 0.33
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Lingua-EN-Sentence
  Assignee: rc040...@freenet.de
  Reporter: jples...@redhat.com
QA Contact: extras...@fedoraproject.org
CC: p...@city-fan.org, perl-devel@lists.fedoraproject.org,
rc040...@freenet.de, xav...@bachelot.org
  Target Milestone: ---
Classification: Fedora



Latest Fedora delivers 0.31 version. Upstream released 0.33. When you have free
time, please upgrade it.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2105954
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2103484] perl-PAR-Packer-1.055 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2103484

Jitka Plesnikova  changed:

   What|Removed |Added

 CC|anon.am...@gmail.com,   |
   |jples...@redhat.com,|
   |mmasl...@redhat.com |
 Status|NEW |ASSIGNED
   Doc Type|--- |If docs needed, set a value




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2103484
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2103378] perl-Socket-2.035 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2103378



--- Comment #1 from Fedora Update System  ---
FEDORA-2022-1a662f3bdc has been submitted as an update to Fedora 36.
https://bodhi.fedoraproject.org/updates/FEDORA-2022-1a662f3bdc


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2103378
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Once again, more than 8 days delayed notifications

[Sérgio Basto]

On Mon, 2022-07-11 at 09:35 +0200, Pierre-Yves Chibon wrote:
> On Sat, Jul 09, 2022 at 09:36:14AM -0400, Stephen Smoogen wrote:
> > On Sat, 9 Jul 2022 at 09:25, Ralf Corsépius 
> > wrote:
> > 
> > > Hi,
> > > 
> > > I thought the notification delay mess was fixed. Apparently, I
> > > was wrong.
> > > 
> > > 
> > 
> > No, I believe the service which is behind these emails is called
> > FMN. It is
> > very fragile for multiple reasons where it falls over for different
> > reasons
> > all the time. It is the reason why it is on the top of being
> > replaced by
> > CPE in this quarter (aka by October-ish). 
> 
> Just a quick note, I doubt the app will be re-written and deploy in a
> single
> quarter, I expect this to be more a multi-months effort. So while it
> has the top
> of the priority list for CPE to work on, it'll still take a little
> time before
> we see a v4 (we've already restructured it 3 times).
> 

I think you should disable the service or allocate someone to do
something that mitigate the problem or reboot the service every time it
stops 



> Pierre
> ___
> 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

-- 
Sérgio M. B.
___
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

[Bug 2103378] perl-Socket-2.035 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2103378

Jitka Plesnikova  changed:

   What|Removed |Added

   Fixed In Version||perl-Socket-2.035-1.fc37
 CC|jples...@redhat.com,|
   |mspa...@redhat.com, |
   |ppi...@redhat.com   |
 Status|ASSIGNED|MODIFIED




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2103378
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2103378] perl-Socket-2.035 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2103378

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
   Doc Type|--- |If docs needed, set a value




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2103378
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Fedora SCM requests on the weekend

[Michal Konecny]

Last time I checked we were stuck on pagure not emitting any messages on 
staging. I will look into this more this week.


I will try to test on tickets that are on 
https://stg.pagure.io/releng/fedora-scm-requests and if they will be 
processed without issue, I plan to deploy it on production. There will 
be probably some hiccups at the start, hopefully we will solve most of 
them on staging.


Michal

On 11. 07. 22 1:19, Kevin Fenzi wrote:

On Sun, Jul 10, 2022 at 06:34:11PM +0200, Simon de Vlieger wrote:

Would you need any help regarding the automation?

Well, I'm not doing the implementation there, but we can always use
help. ;)

I think the code is all there now, we were wanting to get staging
working to test it before rolling it out.

It's being added as a toddler ( https://pagure.io/fedora-infra/toddlers
) which is basically a framework for things that listen to the message
bus and act on messages or run from time to time to do things.

CCing Michal here for comment on where we can use help here.

kevin
--

On Sat, Jul 9, 2022, at 8:10 PM, Kevin Fenzi wrote:

On Fri, Jul 08, 2022 at 01:02:15PM -, Mukundan Ragavan wrote:

On Sun, Jul 03, 2022 at 12:11:40PM +0200, Fabio Valentini wrote:

That said, until then I can try and run things on weekends.

Is there a formal process to volunteer to hold the keys to the kingdom?

Yes. Basically one of the existing group members nominates someone, and
all the existing group members vote on adding them.

However, at this point we are close to automating it, so not sure it's
worth adding more folks. We could though if it isn't automated soon...

kevin

___
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

Attachments:
* signature.asc

___
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

___
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: F37 proposal: Add -fno-omit-frame-pointer to default compilation flags (System-Wide Change proposal)

[Daan De Meyer via devel]

> You still might have LBR buffers deep enough for your purposes, I think
> that's worth checking.  They have been around for much longer (on
> Intel).

We've been using LBR opportunistically for a while if available to augment 
frame 
pointer based stacks. It turns out to be quite helpful at the lowest levels of 
the 
stacktrace where it can help to work around the lack of frame pointers in base 
system libraries or libraries using inline assembly.

32 entries are not sufficient to capture all of our stacktraces though so using
only LBR is not sufficient for our profiling.

Currently we augment the frame pointer stacks with LBR data in userspace but 
I've
asked Andrii to look into doing this augmentation directly in the kernel so that
everyone can benefit from it. I think it might help with cases such as the 
glibc string
functions as well (but you probably know more about that than I do).

> Does your use case actually involve high-frequency time-based profiling,
> or is it more about being able to get the data at all, and process it
> further using BPF?

Yes, we're doing high-frequency sampling profiling using the perf 
subsystem (see the proposal for a detailed description). We attach
BPF programs to perf events for some minimal post processing before 
storing the data.

Cheers,

Daan
___
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: F37 proposal: Add -fno-omit-frame-pointer to default compilation flags (System-Wide Change proposal)

[Florian Weimer]

* Daan De Meyer via devel:

>> If we can get SHSTK to work, the value of the DWARF integration and
>> performance work will diminish fairly quickly because most developers
>> will soon have CPUs with fairly deep (32 entry) LBR buffers, SHSTK
>> support, or both.
>
> This seems like a fairly bold assumption. I also want to add that as
> discussed in the proposal, we want to enable profiling not just on our
> laptops, but across our entire fleet that's running various
> generations of hardware. We can't simply replace all of our hardware
> just to get shadow stack support unfortunately. So we can't rely on
> new hardware features to get stacktraces.

You still might have LBR buffers deep enough for your purposes, I think
that's worth checking.  They have been around for much longer (on
Intel).

Does your use case actually involve high-frequency time-based profiling,
or is it more about being able to get the data at all, and process it
further using BPF?

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

[Bug 2103369] perl-Math-BigInt-1.999837 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2103369

Jitka Plesnikova  changed:

   What|Removed |Added

   Doc Type|--- |If docs needed, set a value
 Resolution|--- |RAWHIDE
   Fixed In Version||perl-Math-BigInt-1.9998.37-
   ||1.fc37
 Status|NEW |CLOSED
Last Closed||2022-07-11 09:04:49




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2103369
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Fedora-Cloud-35-20220711.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-35-20220710.0):

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

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

[Bug 2105868] perl-URI-5.12 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2105868

Paul Howarth  changed:

   What|Removed |Added

 Resolution|--- |RAWHIDE
   Fixed In Version||perl-URI-5.12-1.fc37
 Status|ASSIGNED|CLOSED
Last Closed||2022-07-11 09:02:54



--- Comment #1 from Paul Howarth  ---
Build done:
https://koji.fedoraproject.org/koji/taskinfo?taskID=89364810


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2105868
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Rename Airspy

[Buford T. Justice]

https://bugzilla.redhat.com/show_bug.cgi?id=2105847
___
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: Request: Airspy HF+

[Buford T. Justice]

I went ahead and built it after battling for a month on exactly how to do it 
with Fedora in this world of online instructions being mostly for Ubuntu:

https://groups.io/g/airspy/message/43783

AirSpy HF library version: 1.6.8
___
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: F37 proposal: Add -fno-omit-frame-pointer to default compilation flags (System-Wide Change proposal)

[Daan De Meyer via devel]

> If we can get SHSTK to work, the value of the DWARF integration and
> performance work will diminish fairly quickly because most developers
> will soon have CPUs with fairly deep (32 entry) LBR buffers, SHSTK
> support, or both.

This seems like a fairly bold assumption. I also want to add that as discussed
in the proposal, we want to enable profiling not just on our laptops, but across
our entire fleet that's running various generations of hardware. We can't simply
replace all of our hardware just to get shadow stack support unfortunately. So
we can't rely on new hardware features to get stacktraces.

Of course, if shadow stack support lands upstream, is found to be reliable and 
is
fully supported by all hardware running on our fleet, we'd definitely look into 
using
it instead of frame pointers. But's it's going to take many years before we can 
rely
by all our hardware.

Aside from our use case, I don't think developers are constantly replacing their
hardware either. I'd guess that with this approach we'd have many years of
developers debugging why they're not getting full stacktraces only to find out
their hardware doesn't support shadow stacks.

So to summarize, while we're anxiously awaiting for one of the mentioned
alternatives to become viable, at the moment we think all of them result in a
degraded profiling experience compared to frame pointers, either due to being
slow, being a prototype and not available upstream, or due to requiring new
hardware support.

Cheers,

Daan


From: Florian Weimer 
Sent: 11 July 2022 07:12
To: Matthias Clasen
Cc: Development discussions related to Fedora
Subject: Re: F37 proposal: Add -fno-omit-frame-pointer to default compilation 
flags (System-Wide Change proposal)

* Matthias Clasen:

> On Wed, Jul 6, 2022 at 3:06 PM Florian Weimer  wrote:
>
>> If the GNOME's sysprof does not work with Fedora, fix it or use
>> something else.  Do not change how Fedora is built.
>
> The result of that attitude is that performance work in the desktop
> space is happening on GNOME OS images, or in Flatpak runtimes instead
> of on Fedora. Which is a bit sad for Fedora as a supposedly
> developer-friendly environment.

My comment was specifically about sysprof.  I've been told that the
GNOME developers will not even consider anything else.  This means that
we need to fix sysprof.  If we do that, it will be possible to use GNOME
OS for profiling on older CPUs, and hardware-assisted backtraces on
newer CPUs on Fedora (at least Skylake and Zen 3, especially once we've
got userspace SHSTK support).

Even if this proposal is not accepted, I think we can collaborate on a
couple of things:

* Enhance sysprof with LBR and SHSTK support.

* Enable userspace backtrace generation from BPF without frame pointers
  (possibly by using LBR and SHSTK at first).

* Investigate use of the Systemtap and elfutils unwinders in these
  tools.

* Speed up decoding of DWARF data structures using the BMI instruction
  sets (which only operate on scalar registers and should therefore be
  usable even within the kernel).  According to
  
  that's a major source of DWARF processing overhead, and I don't think
  it has to be.

I'll try to get confirmation that it is technically feasible in priciple
to use SHSTK to get arbitrarily deep backtraces from kernel space for
userspace applications.

If we can get SHSTK to work, the value of the DWARF integration and
performance work will diminish fairly quickly because most developers
will soon have CPUs with fairly deep (32 entry) LBR buffers, SHSTK
support, or both.

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
___
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

[Bug 2105868] perl-URI-5.12 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2105868

Paul Howarth  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
   Assignee|jples...@redhat.com |p...@city-fan.org
   Doc Type|--- |If docs needed, set a value




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2105868
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: proposal idea: EOL notifications

[Artém S . Tashkinóv]

> I am not excited, because I feel it doesn't add any value to Fedora.

It's not about adding "value", it's about making sure that people
realize that they are running unsupported software which no longer
receives updates and might have vulnerabilities, including remote.
Actually, any now unsupported Fedora release has a ton of them. Maybe
that's totally OK for, that's totally not OK for me.

When a person installs a new shiny distro they are not obliged to
subscribe to distro news or mailing lists and that's exactly what most
people do.

Many run their Linux distro headless, so whatever Gnome guys may come up
with will not work for people who only use console/remote SSH shell.

Best regards,
Artem
___
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

[Bug 2105286] Please branch and build perl-Net-SSH in epel8

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2105286

Jitka Plesnikova  changed:

   What|Removed |Added

   Doc Type|--- |If docs needed, set a value
 Status|NEW |ASSIGNED



--- Comment #1 from Jitka Plesnikova  ---
https://pagure.io/releng/fedora-scm-requests/issue/45670


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2105286
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Fedora-Cloud-36-20220711.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-36-20220710.0):

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

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: Once again, more than 8 days delayed notifications

[Pierre-Yves Chibon]

On Sat, Jul 09, 2022 at 09:36:14AM -0400, Stephen Smoogen wrote:
> On Sat, 9 Jul 2022 at 09:25, Ralf Corsépius  wrote:
> 
> > Hi,
> >
> > I thought the notification delay mess was fixed. Apparently, I was wrong.
> >
> >
> 
> No, I believe the service which is behind these emails is called FMN. It is
> very fragile for multiple reasons where it falls over for different reasons
> all the time. It is the reason why it is on the top of being replaced by
> CPE in this quarter (aka by October-ish). 

Just a quick note, I doubt the app will be re-written and deploy in a single
quarter, I expect this to be more a multi-months effort. So while it has the top
of the priority list for CPE to work on, it'll still take a little time before
we see a v4 (we've already restructured it 3 times).

Pierre
___
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: Once again, more than 8 days delayed notifications

[Pierre-Yves Chibon]

On Sat, Jul 09, 2022 at 05:16:55PM +0200, Ralf Corsépius wrote:
> 
> 
> Am 09.07.22 um 15:36 schrieb Stephen Smoogen:
> > 
> > 
> > On Sat, 9 Jul 2022 at 09:25, Ralf Corsépius  > > wrote:
> > 
> > Hi,
> > 
> > I thought the notification delay mess was fixed. Apparently, I was
> > wrong.
> > 
> > 
> > 
> > No, I believe the service which is behind these emails is called FMN. It
> > is very fragile for multiple reasons where it falls over for different
> > reasons all the time. It is the reason why it is on the top of being
> > replaced by CPE in this quarter (aka by October-ish). Until that
> > happens, please be aware that these notifications are likely to come in
> > bursts as things go up and down. I would also suggest that turning off
> > as many notifications as you can would help the load as one of the
> > largest email problems Fedora Infrastructure has is the many people who
> > have turned on getting email on a lot of events.
> 
> Why don't you turn this stuff off globally and send the guys behind it back
> to the drawing board?
> 
> In its present shape it's just dysfunctional and not helpful at all.

It is very much self-service, so you can easily turn off the notifications for
your account if you wish to:
https://apps.fedoraproject.org/notifications


Pierre
___
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

[Bug 2102631] Add perl-Class-C3-Componentised to EPEL 9

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2102631

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED



--- Comment #1 from Jitka Plesnikova  ---
https://pagure.io/releng/fedora-scm-requests/issue/45669


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2102631
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2105287] Please branch and build perl-Net-SSH in epel9

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2105287

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
   Doc Type|--- |If docs needed, set a value



--- Comment #1 from Jitka Plesnikova  ---
https://pagure.io/releng/fedora-scm-requests/issue/45668


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2105287
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: F37 proposal: Add -fno-omit-frame-pointer to default compilation flags (System-Wide Change proposal)

[Florian Weimer]

* Matthias Clasen:

> On Wed, Jul 6, 2022 at 3:06 PM Florian Weimer  wrote:
>  
>> If the GNOME's sysprof does not work with Fedora, fix it or use
>> something else.  Do not change how Fedora is built.
>
> The result of that attitude is that performance work in the desktop
> space is happening on GNOME OS images, or in Flatpak runtimes instead
> of on Fedora. Which is a bit sad for Fedora as a supposedly
> developer-friendly environment.

My comment was specifically about sysprof.  I've been told that the
GNOME developers will not even consider anything else.  This means that
we need to fix sysprof.  If we do that, it will be possible to use GNOME
OS for profiling on older CPUs, and hardware-assisted backtraces on
newer CPUs on Fedora (at least Skylake and Zen 3, especially once we've
got userspace SHSTK support).

Even if this proposal is not accepted, I think we can collaborate on a
couple of things:

* Enhance sysprof with LBR and SHSTK support.

* Enable userspace backtrace generation from BPF without frame pointers
  (possibly by using LBR and SHSTK at first).

* Investigate use of the Systemtap and elfutils unwinders in these
  tools.

* Speed up decoding of DWARF data structures using the BMI instruction
  sets (which only operate on scalar registers and should therefore be
  usable even within the kernel).  According to
  
  that's a major source of DWARF processing overhead, and I don't think
  it has to be.

I'll try to get confirmation that it is technically feasible in priciple
to use SHSTK to get arbitrarily deep backtraces from kernel space for
userspace applications.

If we can get SHSTK to work, the value of the DWARF integration and
performance work will diminish fairly quickly because most developers
will soon have CPUs with fairly deep (32 entry) LBR buffers, SHSTK
support, or both.

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

[Bug 2105822] EPEL 9 is missing needed package for i3

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2105822



--- Comment #2 from Paul Howarth  ---
The perl-JSON-XS package can be found in the Code Ready Builder (RHEL) /
PowerTools (clones) repository. Many EPEL dependencies, particularly for perl
packages, can be found there.

You'll need to enable that repository to get the package.
There has been some discussion recently about auto-enabling this repository
when installing epel-release:
https://www.mail-archive.com/epel-devel@lists.fedoraproject.org/msg09770.html


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2105822
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure