date:20220809

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

Bug ID: 2117117
   Summary: perl-XML-Atom-SimpleFeed-0.905 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-XML-Atom-SimpleFeed
  Keywords: FutureFeature, Triaged
  Assignee: emman...@seyman.fr
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: emman...@seyman.fr, lkund...@v3.sk,
perl-devel@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



Releases retrieved: 0.905
Upstream release that is considered latest: 0.905
Current version/release in rawhide: 0.904-9.fc37
URL: http://search.cpan.org/dist/XML-Atom-SimpleFeed/

Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.


Based on the information from Anitya:
https://release-monitoring.org/project/7550/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/perl-XML-Atom-SimpleFeed


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2117117
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2117116] New: perl-Test-File-Contents-0.241 is available

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

Bug ID: 2117116
   Summary: perl-Test-File-Contents-0.241 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Test-File-Contents
  Keywords: FutureFeature, Triaged
  Assignee: jples...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: iarn...@gmail.com, jples...@redhat.com,
perl-devel@lists.fedoraproject.org, st...@silug.org
  Target Milestone: ---
Classification: Fedora



Releases retrieved: 0.241
Upstream release that is considered latest: 0.241
Current version/release in rawhide: 0.240-2.fc37
URL: http://search.cpan.org/dist/Test-File-Contents/

Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.


Based on the information from Anitya:
https://release-monitoring.org/project/9868/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/perl-Test-File-Contents


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2117116
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2116569] perl-Digest-SHA-6.03 is available

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



--- Comment #6 from Fedora Update System  ---
FEDORA-2022-892c34c9c8 has been pushed to the Fedora 35 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-892c34c9c8`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2022-892c34c9c8

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=2116569
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

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

2022-08-09 Thread updates

The following Fedora EPEL 7 Security updates need testing:
 Age  URL
   1  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-55ddc1978f   
rubygem-tzinfo-1.2.10-1.el7


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

ntfs-3g-2022.5.17-1.el7

Details about builds:



 ntfs-3g-2022.5.17-1.el7 (FEDORA-EPEL-2022-69c4ed93d1)
 Linux NTFS userspace driver

Update Information:

Update to 2022.5.17.  Fixes: CVE-2021-46790, CVE-2022-30783, CVE-2022-30784,
CVE-2022-30785, CVE-2022-30786, CVE-2022-30787, CVE-2022-30788, CVE-2022-30789

ChangeLog:

* Wed Jun  8 2022 Richard W.M. Jones  - 2:2022.5.17-1
- New upstream version 2022.5.17
 - Fixes: CVE-2021-46790, CVE-2022-30783, CVE-2022-30784, CVE-2022-30785,
   CVE-2022-30786, CVE-2022-30787, CVE-2022-30788, CVE-2022-30789

References:

  [ 1 ] Bug #2093307 - CVE-2022-30783 ntfs-3g: invalid return code in 
fuse_kern_mount enables intercepting of libfuse-lite protocol traffic [epel-all]
https://bugzilla.redhat.com/show_bug.cgi?id=2093307
  [ 2 ] Bug #2093317 - CVE-2022-30784 ntfs-3g: crafted NTFS image can cause 
heap exhaustion in ntfs_get_attribute_value [epel-all]
https://bugzilla.redhat.com/show_bug.cgi?id=2093317
  [ 3 ] Bug #2093322 - CVE-2022-30785 ntfs-3g: a file handle created in 
fuse_lib_opendir, and later used in fuse_lib_readdir, enables arbitrary memory 
read and write operations [epel-all]
https://bugzilla.redhat.com/show_bug.cgi?id=2093322
  [ 4 ] Bug #2093330 - CVE-2022-30786 ntfs-3g: crafted NTFS image can cause a 
heap-based buffer overflow in ntfs_names_full_collate [epel-all]
https://bugzilla.redhat.com/show_bug.cgi?id=2093330
  [ 5 ] Bug #2093335 - CVE-2022-30787 ntfs-3g: integer underflow in 
fuse_lib_readdir enables arbitrary memory read operations [epel-all]
https://bugzilla.redhat.com/show_bug.cgi?id=2093335
  [ 6 ] Bug #2093342 - CVE-2022-30788 ntfs-3g: crafted NTFS image can cause a 
heap-based buffer overflow in ntfs_mft_rec_alloc [epel-all]
https://bugzilla.redhat.com/show_bug.cgi?id=2093342
  [ 7 ] Bug #2093350 - CVE-2022-30789 ntfs-3g: crafted NTFS image can cause a 
heap-based buffer overflow in ntfs_check_log_client_array [epel-all]
https://bugzilla.redhat.com/show_bug.cgi?id=2093350
  [ 8 ] Bug #2093362 - CVE-2021-46790 ntfs-3g: heap-based buffer overflow in 
ntfsck [epel-all]
https://bugzilla.redhat.com/show_bug.cgi?id=2093362


___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2117100] New: perl-Proc-Fork-0.807 is available

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

Bug ID: 2117100
   Summary: perl-Proc-Fork-0.807 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Proc-Fork
  Keywords: FutureFeature, Triaged
  Assignee: jples...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: jples...@redhat.com,
perl-devel@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



Releases retrieved: 0.807
Upstream release that is considered latest: 0.807
Current version/release in rawhide: 0.806-13.fc37
URL: http://search.cpan.org/dist/Proc-Fork/

Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.


Based on the information from Anitya:
https://release-monitoring.org/project/6893/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/perl-Proc-Fork


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2117100
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2116568] perl-Digest-SHA3-1.05 is available

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #4 from Fedora Update System  ---
FEDORA-2022-04ed85fdf4 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-04ed85fdf4`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2022-04ed85fdf4

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=2116568
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

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

2022-08-09 Thread updates

The following Fedora EPEL 8 Security updates need testing:
 Age  URL
  20  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-89ad385971   
chromium-103.0.5060.114-1.el8


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

gsi-openssh-8.0p1-10.el8
ntfs-3g-2022.5.17-2.el8

Details about builds:



 gsi-openssh-8.0p1-10.el8 (FEDORA-EPEL-2022-394ad1e696)
 An implementation of the SSH protocol with GSI authentication

Update Information:

Sync patches with openssh

ChangeLog:

* Tue Aug  9 2022 Mattias Ellert  - 8.0p1-10
- Based on openssh-8.0p1-13.el8




 ntfs-3g-2022.5.17-2.el8 (FEDORA-EPEL-2022-111c0bd3f5)
 Linux NTFS userspace driver

Update Information:

Update to 2022.5.17.  Fixes: CVE-2021-46790, CVE-2022-30783, CVE-2022-30784,
CVE-2022-30785, CVE-2022-30786, CVE-2022-30787, CVE-2022-30788, CVE-2022-30789

ChangeLog:

* Fri Jul 22 2022 Fedora Release Engineering  - 
2:2022.5.17-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild
* Wed Jun  8 2022 Richard W.M. Jones  - 2:2022.5.17-1
- New upstream version 2022.5.17
- Fixes: CVE-2021-46790, CVE-2022-30783, CVE-2022-30784, CVE-2022-30785,
  CVE-2022-30786, CVE-2022-30787, CVE-2022-30788, CVE-2022-30789
* Thu Jan 20 2022 Fedora Release Engineering  - 
2:2021.8.22-5
- Rebuilt for https://fedoraproject.org/wiki/Fedora_36_Mass_Rebuild
* Wed Sep 15 2021 Neal Gompa  - 2:2021.8.22-4
- Restyle the spec for legibility
* Mon Sep 13 2021 Richard W.M. Jones  - 2:2021.8.22-3
- Remove unused ntfsprogs/boot.c replacement

References:

  [ 1 ] Bug #2093307 - CVE-2022-30783 ntfs-3g: invalid return code in 
fuse_kern_mount enables intercepting of libfuse-lite protocol traffic [epel-all]
https://bugzilla.redhat.com/show_bug.cgi?id=2093307
  [ 2 ] Bug #2093317 - CVE-2022-30784 ntfs-3g: crafted NTFS image can cause 
heap exhaustion in ntfs_get_attribute_value [epel-all]
https://bugzilla.redhat.com/show_bug.cgi?id=2093317
  [ 3 ] Bug #2093322 - CVE-2022-30785 ntfs-3g: a file handle created in 
fuse_lib_opendir, and later used in fuse_lib_readdir, enables arbitrary memory 
read and write operations [epel-all]
https://bugzilla.redhat.com/show_bug.cgi?id=2093322
  [ 4 ] Bug #2093330 - CVE-2022-30786 ntfs-3g: crafted NTFS image can cause a 
heap-based buffer overflow in ntfs_names_full_collate [epel-all]
https://bugzilla.redhat.com/show_bug.cgi?id=2093330
  [ 5 ] Bug #2093335 - CVE-2022-30787 ntfs-3g: integer underflow in 
fuse_lib_readdir enables arbitrary memory read operations [epel-all]
https://bugzilla.redhat.com/show_bug.cgi?id=2093335
  [ 6 ] Bug #2093342 - CVE-2022-30788 ntfs-3g: crafted NTFS image can cause a 
heap-based buffer overflow in ntfs_mft_rec_alloc [epel-all]
https://bugzilla.redhat.com/show_bug.cgi?id=2093342
  [ 7 ] Bug #2093350 - CVE-2022-30789 ntfs-3g: crafted NTFS image can cause a 
heap-based buffer overflow in ntfs_check_log_client_array [epel-all]
https://bugzilla.redhat.com/show_bug.cgi?id=2093350
  [ 8 ] Bug #2093362 - CVE-2021-46790 ntfs-3g: heap-based buffer overflow in 
ntfsck [epel-all]
https://bugzilla.redhat.com/show_bug.cgi?id=2093362


___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2116569] perl-Digest-SHA-6.03 is available

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #5 from Fedora Update System  ---
FEDORA-2022-4dd5aa4cdb 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-4dd5aa4cdb`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2022-4dd5aa4cdb

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=2116569
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2116538] perl-DBD-Pg-3.16.0 is available

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #2 from Fedora Update System  ---
FEDORA-2022-9745012975 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-9745012975`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2022-9745012975

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=2116538
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2112642] perlbrew-0.96 is available

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ON_QA   |CLOSED
   Fixed In Version|perlbrew-0.96-1.fc37|perlbrew-0.96-1.fc37
   ||perlbrew-0.96-1.fc36
 Resolution|--- |ERRATA
Last Closed||2022-08-10 01:15:53



--- Comment #3 from Fedora Update System  ---
FEDORA-2022-c650c63e92 has been pushed to the Fedora 36 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=2112642
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: [HEADS UP] wxPython 4.2.0 in Rawhide


On 8/9/22 06:00 PM, Scott Talbert wrote:

On Tue, 9 Aug 2022, Steven A. Falco wrote:


On 8/9/22 05:06 PM, Scott Talbert wrote:

On Tue, 9 Aug 2022, Steven A. Falco wrote:


On 8/9/22 02:25 PM, Steven A. Falco wrote:

On 8/9/22 01:09 PM, Scott Talbert wrote:

Hi,

Upstream wxPython has finally made a new release and this involves migrating to 
wxWidgets 3.2.0 at the same time.  I'm planning to build the new wxPython in 
Rawhide after F37 branch (although could put it in F37 later).

For those packages that use both wxPython and wxWidgets (I *think* this is just 
kicad?), do you want me to do this in a side-tag so we can switch the packages 
at the same time?  Or just build in rawhide and let you fix things up?


That is very good news, Scott.  The upstream KiCad devs are working on 3.2.0 
right now, as part of their efforts to support the new M1 Apple machines.

If KiCad is the only customer, I'd say there is no need to do a side-tag, 
unless that is easier for you.  I'm fine either way.


I should add that I would like to see this in F37 at some point, because that 
will help with retiring the old wxWidgets code from KiCad sooner.


Yeah, we can get the changes into F37.

So KiCad isn't quite ready to move yet?  I can hold off until you're ready.


I've spoken with the upstream KiCad developers, and based on that conversation 
I think you should go ahead and put the new wxWidgets / wxPython into Rawhide 
when it is convenient for you, without waiting for KiCad.

There is a KiCad Copr [1], where we make nightly pre-release builds of what 
will become the KiCad 7.x series, with 7.0.0 probably releasing towards the end 
of the year.  The KiCad 7 series is where the upstream devs prefer to integrate 
with the new wxWidgets / wxPython both because of the risk of new bugs and also 
so they don't have to backport fixes to the older KiCad 6.x series.

So, once you have the new wxWidgets / wxPython in Rawhide, I'll try it out 
locally and in our Copr.  Based on how that goes, we can consider switching 
over the downstream Rawhide builds.  But based on the way the timing has worked 
out, and because we don't want to do a major version upgrade of KiCad in a 
stable Fedora release, we may not be able to switch KiCad to the new wxWidgets 
/ wxPython in F37.


The problem though, is that while wxWidgets versions are parallel installable, 
wxPython versions are not.  So, once I update to wxPython 4.2.0 (which links 
with wxWidgets 3.2.0), wxPython 4.0.7 will be gone. I'm presuming that's going 
to break KiCad?


It is a bit awkward to be mediating between the Fedora devel list and the KiCad 
one, but I think we are nearly there.  According to one of the KiCad leads:

"The Flatpak has been running the wx 3.1 branch since v6 was released, and so far 
there have been no issues. We already have Windows and macOS running the 3.1 versions, so 
I don't see why we need to hold the Linux builds back."

So, I think we are good to go forward and retire wxPython 4.0.7 at your 
convenience.  If it is not too much trouble to use a side-tag, I'll make the 
KiCad build there and it can all go in together.  My schedule is quite open, so 
I shouldn't hold you up.

Please let me know whenever you are ready.  No rush.  And thanks for your 
patience. :-)

Steve



___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2117083] New: perl-Parallel-Iterator-1.002 is available

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

Bug ID: 2117083
   Summary: perl-Parallel-Iterator-1.002 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Parallel-Iterator
  Keywords: FutureFeature, Triaged
  Assignee: jples...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: iarn...@gmail.com, jples...@redhat.com,
perl-devel@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



Releases retrieved: 1.002
Upstream release that is considered latest: 1.002
Current version/release in rawhide: 1.001-1.fc37
URL: https://metacpan.org/dist/Parallel-Iterator

Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.


Based on the information from Anitya:
https://release-monitoring.org/project/12769/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/perl-Parallel-Iterator


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2117083
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2117075] New: perl-XML-XPath-1.48 is available

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

Bug ID: 2117075
   Summary: perl-XML-XPath-1.48 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-XML-XPath
  Keywords: FutureFeature, Triaged
  Assignee: jples...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: jples...@redhat.com, ka...@ucw.cz, mspa...@redhat.com,
perl-devel@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



Releases retrieved: 1.48
Upstream release that is considered latest: 1.48
Current version/release in rawhide: 1.47-3.fc37
URL: http://search.cpan.org/dist/XML-XPath/

Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.


Based on the information from Anitya:
https://release-monitoring.org/project/3544/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/perl-XML-XPath


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2117075
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: [HEADS UP] wxPython 4.2.0 in Rawhide


On Tue, 9 Aug 2022, Steven A. Falco wrote:


On 8/9/22 05:06 PM, Scott Talbert wrote:

On Tue, 9 Aug 2022, Steven A. Falco wrote:


On 8/9/22 02:25 PM, Steven A. Falco wrote:

On 8/9/22 01:09 PM, Scott Talbert wrote:

Hi,

Upstream wxPython has finally made a new release and this involves 
migrating to wxWidgets 3.2.0 at the same time.  I'm planning to build 
the new wxPython in Rawhide after F37 branch (although could put it in 
F37 later).


For those packages that use both wxPython and wxWidgets (I *think* this 
is just kicad?), do you want me to do this in a side-tag so we can 
switch the packages at the same time?  Or just build in rawhide and let 
you fix things up?


That is very good news, Scott.  The upstream KiCad devs are working on 
3.2.0 right now, as part of their efforts to support the new M1 Apple 
machines.


If KiCad is the only customer, I'd say there is no need to do a side-tag, 
unless that is easier for you.  I'm fine either way.


I should add that I would like to see this in F37 at some point, because 
that will help with retiring the old wxWidgets code from KiCad sooner.


Yeah, we can get the changes into F37.

So KiCad isn't quite ready to move yet?  I can hold off until you're ready.


I've spoken with the upstream KiCad developers, and based on that 
conversation I think you should go ahead and put the new wxWidgets / wxPython 
into Rawhide when it is convenient for you, without waiting for KiCad.


There is a KiCad Copr [1], where we make nightly pre-release builds of what 
will become the KiCad 7.x series, with 7.0.0 probably releasing towards the 
end of the year.  The KiCad 7 series is where the upstream devs prefer to 
integrate with the new wxWidgets / wxPython both because of the risk of new 
bugs and also so they don't have to backport fixes to the older KiCad 6.x 
series.


So, once you have the new wxWidgets / wxPython in Rawhide, I'll try it out 
locally and in our Copr.  Based on how that goes, we can consider switching 
over the downstream Rawhide builds.  But based on the way the timing has 
worked out, and because we don't want to do a major version upgrade of KiCad 
in a stable Fedora release, we may not be able to switch KiCad to the new 
wxWidgets / wxPython in F37.


The problem though, is that while wxWidgets versions are parallel 
installable, wxPython versions are not.  So, once I update to wxPython 
4.2.0 (which links with wxWidgets 3.2.0), wxPython 4.0.7 will be gone. 
I'm presuming that's going to break KiCad?


Scott___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: [HEADS UP] wxPython 4.2.0 in Rawhide


On 8/9/22 05:06 PM, Scott Talbert wrote:

On Tue, 9 Aug 2022, Steven A. Falco wrote:


On 8/9/22 02:25 PM, Steven A. Falco wrote:

On 8/9/22 01:09 PM, Scott Talbert wrote:

Hi,

Upstream wxPython has finally made a new release and this involves migrating to 
wxWidgets 3.2.0 at the same time.  I'm planning to build the new wxPython in 
Rawhide after F37 branch (although could put it in F37 later).

For those packages that use both wxPython and wxWidgets (I *think* this is just 
kicad?), do you want me to do this in a side-tag so we can switch the packages 
at the same time?  Or just build in rawhide and let you fix things up?


That is very good news, Scott.  The upstream KiCad devs are working on 3.2.0 
right now, as part of their efforts to support the new M1 Apple machines.

If KiCad is the only customer, I'd say there is no need to do a side-tag, 
unless that is easier for you.  I'm fine either way.


I should add that I would like to see this in F37 at some point, because that 
will help with retiring the old wxWidgets code from KiCad sooner.


Yeah, we can get the changes into F37.

So KiCad isn't quite ready to move yet?  I can hold off until you're ready.


I've spoken with the upstream KiCad developers, and based on that conversation 
I think you should go ahead and put the new wxWidgets / wxPython into Rawhide 
when it is convenient for you, without waiting for KiCad.

There is a KiCad Copr [1], where we make nightly pre-release builds of what 
will become the KiCad 7.x series, with 7.0.0 probably releasing towards the end 
of the year.  The KiCad 7 series is where the upstream devs prefer to integrate 
with the new wxWidgets / wxPython both because of the risk of new bugs and also 
so they don't have to backport fixes to the older KiCad 6.x series.

So, once you have the new wxWidgets / wxPython in Rawhide, I'll try it out 
locally and in our Copr.  Based on how that goes, we can consider switching 
over the downstream Rawhide builds.  But based on the way the timing has worked 
out, and because we don't want to do a major version upgrade of KiCad in a 
stable Fedora release, we may not be able to switch KiCad to the new wxWidgets 
/ wxPython in F37.

Steve

[1] https://copr.fedorainfracloud.org/coprs/g/kicad/kicad/
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Process to remove "abandoned" packages?

2022-08-09 Thread Fabio Valentini

On Tue, Aug 9, 2022 at 5:30 PM Mattia Verga via devel
 wrote:
>
> Il 09/08/22 13:21, Miro Hrončok ha scritto:
> > On 09. 08. 22 13:06, Vít Ondruch wrote:
> >> You can't retire package with provenpackager powers. If that was possible, 
> >> I'd
> >> probably do that.
> > Actually, you can.
> >
> Yep, you can, but then the package will be in a "weird" state. I've
> actually retired a few packages on behalf of the former maintainer, but
> now the packages are retired but not orphaned and only the maintainer
> can orphan them (or I should file a ticket).

That is not a weird state at all, but the intended outcome.
Just because a package will be removed from rawhide (and / or
branched) does not mean that the maintainer does not want to continue
maintaining it in stable branches.

We already have a policy that orphans packages that are retired on
*all branches*, which seems to be what you want.
But orphaning a package that is retired in rawhide but still
maintained in stable branches ... not an intended outcome, in my
opinion.

> BTW, it would be nice if the package list in src.fp.o could be filtered
> out of retired packages so that users can focus on current owned
> packages. Or, maybe, users should be able to remove themselves from
> commit/collaborator rights (actually only admins can add / remove users
> and groups).

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

Re: [HEADS UP] wxPython 4.2.0 in Rawhide


On Tue, 9 Aug 2022, Steven A. Falco wrote:


On 8/9/22 02:25 PM, Steven A. Falco wrote:

On 8/9/22 01:09 PM, Scott Talbert wrote:

Hi,

Upstream wxPython has finally made a new release and this involves 
migrating to wxWidgets 3.2.0 at the same time.  I'm planning to build the 
new wxPython in Rawhide after F37 branch (although could put it in F37 
later).


For those packages that use both wxPython and wxWidgets (I *think* this is 
just kicad?), do you want me to do this in a side-tag so we can switch the 
packages at the same time?  Or just build in rawhide and let you fix 
things up?


That is very good news, Scott.  The upstream KiCad devs are working on 
3.2.0 right now, as part of their efforts to support the new M1 Apple 
machines.


If KiCad is the only customer, I'd say there is no need to do a side-tag, 
unless that is easier for you.  I'm fine either way.


I should add that I would like to see this in F37 at some point, because that 
will help with retiring the old wxWidgets code from KiCad sooner.


Yeah, we can get the changes into F37.

So KiCad isn't quite ready to move yet?  I can hold off until you're 
ready.


Scott___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Process to remove "abandoned" packages?

2022-08-09 Thread Miroslav Suchý


Dne 09. 08. 22 v 12:20 Vít Ondruch napsal(a):


However, if I really wanted to do this, I'd need to ask Mo, possibly use unresponsive maintainer policy. But that is 
too much hassle, so I'll probably leave it alone. 


Seems to me like similar process to what you suggests. The timeout will be 
likely the same.

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

[Bug 2117024] List of components above seems to be out of sync with "current" components

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

Emmanuel Seyman  changed:

   What|Removed |Added

  Component|bugzilla|Reporting/Charting
Product|Fedora  |Bugzilla
   Assignee|emman...@seyman.fr  |bugbot@bot.bugzilla.redhat.
   ||com
   Doc Type|--- |If docs needed, set a value
Version|rawhide |5.0
 QA Contact|extras...@fedoraproject.org |




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2117024
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: [Fedocal] Reminder meeting : Prioritized bugs and issues

2022-08-09 Thread Ben Cotton

A rather important scheduling conflict has arisen, so there will be no
prioritized bugs meeting this week.

-- 
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2117021] change component after adding other data erased all previously entered data causes loss of previously entered tata

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

Emmanuel Seyman  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
Product|Fedora  |Bugzilla
 QA Contact|extras...@fedoraproject.org |
   Assignee|emman...@seyman.fr  |bugbot@bot.bugzilla.redhat.
   ||com
 Status|NEW |CLOSED
Version|rawhide |5.0
  Component|bugzilla|Creating/Changing Bugs
   Doc Type|--- |If docs needed, set a value
Last Closed||2022-08-09 19:07:36



--- Comment #1 from Emmanuel Seyman  ---


*** This bug has been marked as a duplicate of bug 2075768 ***


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2117021
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2117021] change component after adding other data erased all previously entered data causes loss of previously entered tata

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

George R. Goffe  changed:

   What|Removed |Added

Summary|change component after  |change component after
   |adding other data erased|adding other data erased
   |all previously entered data |all previously entered data
   ||causes loss of previously
   ||entered tata




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2117021
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2075768] selecting the 'Component' at the end, cleares the 'Description'

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

Emmanuel Seyman  changed:

   What|Removed |Added

 CC||grgo...@yahoo.com



--- Comment #4 from Emmanuel Seyman  ---
*** Bug 2117021 has been marked as a duplicate of this bug. ***


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2075768
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2117024] New: List of components above seems to be out of sync with "current" components

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

Bug ID: 2117024
   Summary: List of components above seems to be out of sync with
"current" components
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: bugzilla
  Assignee: emman...@seyman.fr
  Reporter: grgo...@yahoo.com
QA Contact: extras...@fedoraproject.org
CC: as...@ionic.at, emman...@seyman.fr,
perl-devel@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



Description of problem:
Attempting to submit a bug generated by dnf upgrade command called out
components NOT listed in "Component" list above

Version-Release number of selected component (if applicable): Current Bugzilla


How reproducible: Always


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2117024
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2117021] New: change component after adding other data erased all previously entered data

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

Bug ID: 2117021
   Summary: change component after adding other data erased all
previously entered data
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: bugzilla
  Assignee: emman...@seyman.fr
  Reporter: grgo...@yahoo.com
QA Contact: extras...@fedoraproject.org
CC: as...@ionic.at, emman...@seyman.fr,
perl-devel@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



Description of problem: Attempting to enter a bug report but the component I
entered was not accepted. I tried to submit the bug report but was prompted to
enter a component which I did. This update triggered the LOSS of all previously
entered data.


Version-Release number of selected component (if applicable): Current bugzilla
level


How reproducible: unknown


Steps to Reproduce: see above
1.
2.
3.

Actual results: see above


Expected results: The SUCCESSFUL generation of a bug report without having to
re-enter all bug information.


Additional info:

I seem to recall reporting this bug some time ago... several years ago? Now
it's back? Argh!


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2117021
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Request for assistance: zfs-fuse

2022-08-09 Thread Vitaly Zaitsev via devel


On 09/08/2022 20:17, Gwyn Ciesla via devel wrote:

+ export CCFLAGS=-O2 -flto=auto -ffat-lto-objects -fexceptions -g 
-grecord-gcc-switches


Export must be quoted. GCC compiler options - must not.

Try removing optim='%{optflags}' from your SPEC. It should automatically 
pick flags from $CCFLAGS.


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

Re: Request for assistance: zfs-fuse

2022-08-09 Thread Gwyn Ciesla via devel



--- Original Message ---
On Tuesday, August 9th, 2022 at 1:31 PM, Daniel P. Berrangé 
 wrote:


> On Tue, Aug 09, 2022 at 04:51:03PM +, Gwyn Ciesla via devel wrote:
> 

> > Good morning!
> > 

> > zfs-fuse is FTBFS starting with f36.
> > 

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

> > I've been banging my head on it for a long time, to no avail. I can get 
> > around the SConstruct failure by removing some environment variables, and 
> > then I hit a linking issue I can't get past.
> 

> 

> Most problems are caused by GCC 10 no longer merging duplicate global
> variable storage. This was super tedios to resolve. I started with
> the gcc10_fixes.patch from Debian and had to tweak it even more.
> 

> A build system bug was causing the extra quotes in compiler options.
> 

> The code is broken wrt -Wformat-security. So this has to be turned
> off, unless someone wants to audit all the printf() calls and fix
> them up. I'd recommend the latter really, but I attach the quick
> fix since that is at least no more awful than it has been for every
> Fedora release previously.
> 

> So in the RPM spec add
> 

> diff --git a/zfs-fuse.spec b/zfs-fuse.spec
> index b26c656..84b6eb0 100644
> --- a/zfs-fuse.spec
> +++ b/zfs-fuse.spec
> @@ -17,6 +17,8 @@ Patch0: zfs-fuse-0.7.2.2-stack.patch
> Patch1: zfs-fuse-0.7.2.2-python3.patch
> Patch2: tirpc.patch
> Patch3: common.patch
> +Patch4: gcc.patch
> +
> BuildRequires: gcc
> BuildRequires: fuse-devel libaio-devel perl-generators scons gcc-c++
> BuildRequires: zlib-devel openssl-devel libattr-devel lzo-devel bzip2-devel 
> xz-devel
> @@ -50,6 +52,7 @@ operating system.
> %patch1 -p1
> %patch2 -p1
> %patch3 -p0
> +%patch4 -p1
> 

> f=LICENSE
> mv $f $f.iso88591
> @@ -63,6 +66,7 @@ chmod -x contrib/zfsstress.py
> cp -f /usr/lib/rpm/redhat/config.{guess,sub} src/lib/libumem/
> 

> %build
> +%define _warning_options '-Wall'
> export CCFLAGS="%{optflags}"
> pushd src
> 

> 

> The gcc.patch is attached.
> 

> > Only libguestfs and libvirt require this, other that users with
> > ZFS filesystems, but I'd rather not retire it if it can be avoided.
> 

> 

> Don't let libvirt/libguestfs force you to keep maintaining zfs-fuse.
> 

> If you want to retire it, we'll just disable zfs in libvirt/libguestfs.
> 

> Honestly I'd retire it, given it is dead upstream, unless someone
> wants to re-incarnate the upstream project and bring the code upto
> modern standards. Even with the patches there's still tonnes of
> (non-fatal) compiler warnings that really ought to be evaluated
> for correctness.

That did the trick, thank you! 


I'd like to keep it around at least for awhile. I'm not sure it's worth that 
level of maintenance, at least by me, who doesn't use ZFS. It *is* worth quick 
fixes like this, IMHO.


> With regards,
> Daniel
> --
> |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
> |: https://libvirt.org -o- https://fstop138.berrange.com :|
> |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|

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

Re: PSA: koji armv7hl builders locking up

2022-08-09 Thread Kevin Fenzi

On Tue, Aug 09, 2022 at 09:14:17AM -0400, Steve Dickson wrote:
> 
> 
> On 8/7/22 3:49 PM, Kevin Fenzi wrote:
> > Or just wait... I have been checking them a few times a day and
> > rebooting any that are locked up.
> How long do we have to wait? [1] has been stuck since
> Mon, 08 Aug 2022 14:17:44 UTC
> 
> steved.
> 
> [1] https://koji.fedoraproject.org/koji/taskinfo?taskID=90612742

Thats one I rebooted this morning after I woke up (and your build is
finished). I am not sure why I didn't see that one as stuck yesterday,
perhaps there's two failure modes here. ;( 

kevin


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

Re: [HEADS UP] wxPython 4.2.0 in Rawhide


On 8/9/22 02:25 PM, Steven A. Falco wrote:

On 8/9/22 01:09 PM, Scott Talbert wrote:

Hi,

Upstream wxPython has finally made a new release and this involves migrating to 
wxWidgets 3.2.0 at the same time.  I'm planning to build the new wxPython in 
Rawhide after F37 branch (although could put it in F37 later).

For those packages that use both wxPython and wxWidgets (I *think* this is just 
kicad?), do you want me to do this in a side-tag so we can switch the packages 
at the same time?  Or just build in rawhide and let you fix things up?


That is very good news, Scott.  The upstream KiCad devs are working on 3.2.0 
right now, as part of their efforts to support the new M1 Apple machines.

If KiCad is the only customer, I'd say there is no need to do a side-tag, 
unless that is easier for you.  I'm fine either way.


I should add that I would like to see this in F37 at some point, because that 
will help with retiring the old wxWidgets code from KiCad sooner.

Steve
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Request for assistance: zfs-fuse

2022-08-09 Thread Daniel P . Berrangé

On Tue, Aug 09, 2022 at 04:51:03PM +, Gwyn Ciesla via devel wrote:
> Good morning!
> 
> zfs-fuse is FTBFS starting with f36.
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=2047144
> 
> I've been banging my head on it for a long time, to no avail. I can get 
> around the SConstruct failure by removing some environment variables, and 
> then I hit a linking issue I can't get past.

Most problems are caused by GCC 10 no longer merging duplicate global
variable storage. This was super tedios to resolve. I started with
the gcc10_fixes.patch from Debian and had to tweak it even more.

A build system bug was causing the extra quotes in compiler options.

The code is broken wrt -Wformat-security. So this has to be turned
off, unless someone wants to audit all the printf() calls and fix
them up. I'd recommend the latter really, but I attach the quick
fix since that is at least no more awful than it has been for every
Fedora release previously.

So in the RPM spec add

diff --git a/zfs-fuse.spec b/zfs-fuse.spec
index b26c656..84b6eb0 100644
--- a/zfs-fuse.spec
+++ b/zfs-fuse.spec
@@ -17,6 +17,8 @@ Patch0:   zfs-fuse-0.7.2.2-stack.patch
 Patch1:   zfs-fuse-0.7.2.2-python3.patch
 Patch2:   tirpc.patch
 Patch3:   common.patch
+Patch4:   gcc.patch
+
 BuildRequires:  gcc
 BuildRequires:fuse-devel libaio-devel perl-generators scons gcc-c++
 BuildRequires:zlib-devel openssl-devel libattr-devel lzo-devel bzip2-devel 
xz-devel
@@ -50,6 +52,7 @@ operating system.
 %patch1 -p1
 %patch2 -p1
 %patch3 -p0
+%patch4 -p1
 
 f=LICENSE
 mv $f $f.iso88591
@@ -63,6 +66,7 @@ chmod -x contrib/zfsstress.py
 cp -f /usr/lib/rpm/redhat/config.{guess,sub} src/lib/libumem/
 
 %build
+%define _warning_options '-Wall'
 export CCFLAGS="%{optflags}"
 pushd src
 

The gcc.patch is attached.

> Only libguestfs and libvirt require this, other that users with
> ZFS filesystems, but I'd rather not retire it if it can be avoided.

Don't let libvirt/libguestfs force you to keep maintaining zfs-fuse.

If you want to retire it, we'll just disable zfs in libvirt/libguestfs.

Honestly I'd retire it, given it is dead upstream, unless someone
wants to re-incarnate the upstream project and bring the code upto
modern standards.  Even with the patches there's still tonnes of
(non-fatal) compiler warnings that really ought to be evaluated
for correctness.

With regards,
Daniel
-- 
|: https://berrange.com  -o-https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o-https://fstop138.berrange.com :|
|: https://entangle-photo.org-o-https://www.instagram.com/dberrange :|
diff -x src/lib/libsolkerncompat/include/sys/utsname.h -rup 
zfs-fuse-0.7.2.2.orig/src/cmd/mount_zfs/mount_zfs.c 
zfs-fuse-0.7.2.2.new/src/cmd/mount_zfs/mount_zfs.c
--- zfs-fuse-0.7.2.2.orig/src/cmd/mount_zfs/mount_zfs.c 2015-11-24 
11:32:31.0 -0500
+++ zfs-fuse-0.7.2.2.new/src/cmd/mount_zfs/mount_zfs.c  2022-08-09 
14:09:10.011720713 -0400
@@ -35,6 +35,7 @@
 #include 
 
 libzfs_handle_t *g_zfs;
+int aok;
 
 typedef struct option_map {
const char *name;
diff -x src/lib/libsolkerncompat/include/sys/utsname.h -rup 
zfs-fuse-0.7.2.2.orig/src/cmd/zfs/zfs_main.c 
zfs-fuse-0.7.2.2.new/src/cmd/zfs/zfs_main.c
--- zfs-fuse-0.7.2.2.orig/src/cmd/zfs/zfs_main.c2022-08-09 
13:12:22.885797414 -0400
+++ zfs-fuse-0.7.2.2.new/src/cmd/zfs/zfs_main.c 2022-08-09 14:11:52.170622824 
-0400
@@ -57,6 +57,7 @@
 #include "zfs_comutil.h"
 
 libzfs_handle_t *g_zfs;
+int aok;
 
 static FILE *mnttab_file;
 static char history_str[HIS_MAX_RECORD_LEN];
diff -x src/lib/libsolkerncompat/include/sys/utsname.h -rup 
zfs-fuse-0.7.2.2.orig/src/cmd/zfs/zfs_util.h 
zfs-fuse-0.7.2.2.new/src/cmd/zfs/zfs_util.h
--- zfs-fuse-0.7.2.2.orig/src/cmd/zfs/zfs_util.h2015-11-24 
11:32:31.0 -0500
+++ zfs-fuse-0.7.2.2.new/src/cmd/zfs/zfs_util.h 2022-08-09 14:05:33.980183340 
-0400
@@ -34,7 +34,7 @@ extern "C" {
 
 void * safe_malloc(size_t size);
 void nomem(void);
-libzfs_handle_t *g_zfs;
+extern libzfs_handle_t *g_zfs;
 
 #ifdef __cplusplus
 }
diff -x src/lib/libsolkerncompat/include/sys/utsname.h -rup 
zfs-fuse-0.7.2.2.orig/src/cmd/zpool/zpool_main.c 
zfs-fuse-0.7.2.2.new/src/cmd/zpool/zpool_main.c
--- zfs-fuse-0.7.2.2.orig/src/cmd/zpool/zpool_main.c2015-11-24 
11:32:31.0 -0500
+++ zfs-fuse-0.7.2.2.new/src/cmd/zpool/zpool_main.c 2022-08-09 
14:13:03.659138821 -0400
@@ -53,6 +53,8 @@
 #include "statcommon.h"
 #include "format.h"
 
+int aok;
+
 static int zpool_do_create(int, char **);
 static int zpool_do_destroy(int, char **);
 
@@ -181,6 +183,8 @@ static char history_str[HIS_MAX_RECORD_L
 
 static uint_t timestamp_fmt = NODATE;
 
+libzfs_handle_t *g_zfs;
+
 static const char *
 get_usage(zpool_help_t idx) {
switch (idx) {
diff -x src/lib/libsolkerncompat/include/sys/utsname.h -rup 
zfs-fuse-0.7.2.2.orig/src/cmd/zpool/zpool_util.h 
zfs-fuse-0.7.2.2.new/src/cmd/zpool/zpool_util.h
---

Re: Request for assistance: zfs-fuse

2022-08-09 Thread Nathanael D. Noblet

On Tue, 2022-08-09 at 18:17 +, Gwyn Ciesla via devel wrote:
> 
> 
> > gcc -o cmd/mount_zfs/mount_zfs.o -c "-O2 -flto=auto -ffat-lto-
> > objects
> > -fexceptions -g -grecord-gcc-switches -pipe -Wall
> > -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2
> > -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-
> > hardened-cc1
> > -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-
> > cc1
> > -m64 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables
> > -fstack-clash-protection" -pipe -Wall -std=c99 -Wno-switch -Wno-
> > unused
> > -Wno-missing-braces -Wno-parentheses -Wno-uninitialized -Wcast-
> > align
> > -fno-strict-aliasing -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -
> > D_REENTRANT
> > -DTEXT_DOMAIN=\"zfs-fuse\" -ggdb -DDEBUG -fPIC -DLINUX_AIO
> > -I/usr/include/tirpc -Ilib/libuutil/include -Ilib/libnvpair/include
> > -Ilib/libumem/include -Ilib/libzfscommon/include -
> > Ilib/libzpool/include
> > -Ilib/libzfs/include -Ilib/libsolcompat/include -
> > Ilib/libavl/include
> > cmd/mount_zfs/mount_zfs.c
> > cc1: error: argument to '-O' should be a non-negative integer, 'g',
> > 's',
> > 'z' or 'fast'
> > 
> 
> Doesn't help:
> 
> + '[' -f /usr/lib/rpm/generate-rpm-note.sh ']'
> + /usr/lib/rpm/generate-rpm-note.sh zfs-fuse 0.7.2.2-22.fc38 x86_64
> + cd zfs-fuse-0.7.2.2
> + export CCFLAGS=-O2 -flto=auto -ffat-lto-objects -fexceptions -g -
> grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-
> D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -
> specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-
> strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -
> mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -
> fcf-protection
> + CCFLAGS=-O2
> /var/tmp/rpm-tmp.u56vY5: line 42: export: `-flto=auto': not a valid
> identifier
> /var/tmp/rpm-tmp.u56vY5: line 42: export: `-ffat-lto-objects': not a
> valid identifier
> /var/tmp/rpm-tmp.u56vY5: line 42: export: `-fexceptions': not a valid
> identifier
> /var/tmp/rpm-tmp.u56vY5: line 42: export: `-g': not a valid
> identifier
> /var/tmp/rpm-tmp.u56vY5: line 42: export: `-grecord-gcc-switches':
> not a valid identifier
> /var/tmp/rpm-tmp.u56vY5: line 42: export: `-pipe': not a valid
> identifier
> /var/tmp/rpm-tmp.u56vY5: line 42: export: `-Wall': not a valid
> identifier
> /var/tmp/rpm-tmp.u56vY5: line 42: export: `-Werror=format-security':
> not a valid identifier
> /var/tmp/rpm-tmp.u56vY5: line 42: export: `-Wp,-D_FORTIFY_SOURCE=2':
> not a valid identifier
> /var/tmp/rpm-tmp.u56vY5: line 42: export: `-Wp,-
> D_GLIBCXX_ASSERTIONS': not a valid identifier
> /var/tmp/rpm-tmp.u56vY5: line 42: export: `-
> specs=/usr/lib/rpm/redhat/redhat-hardened-cc1': not a valid
> identifier
> /var/tmp/rpm-tmp.u56vY5: line 42: export: `-fstack-protector-strong':
> not a valid identifier
> /var/tmp/rpm-tmp.u56vY5: line 42: export: `-
> specs=/usr/lib/rpm/redhat/redhat-annobin-cc1': not a valid identifier
> /var/tmp/rpm-tmp.u56vY5: line 42: export: `-m64': not a valid
> identifier
> /var/tmp/rpm-tmp.u56vY5: line 42: export: `-mtune=generic': not a
> valid identifier
> /var/tmp/rpm-tmp.u56vY5: line 42: export: `-fasynchronous-unwind-
> tables': not a valid identifier
> /var/tmp/rpm-tmp.u56vY5: line 42: export: `-fstack-clash-protection':
> not a valid identifier
> /var/tmp/rpm-tmp.u56vY5: line 42: export: `-fcf-protection': not a
> valid identifier
> error: Bad exit status from /var/tmp/rpm-tmp.u56vY5 (%build)
> 


I'm no expert but you're hitting two different issues. Your first error
message was running the compilre gcc with options being quoted.

gcc -o cmd/mount_zfs/mount_zfs.o -c "-O2 -flto=auto "

The second is when the environment variable is being exported.

export CCFLAGS=-O2 -flto=auto ...

I think you want export CCFLAGS="-O2 -flto=auto" and the gcc line to
not quote the env var.

Maybe post the spec somewhere?

Sincerely,
-- 
Nathanael
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: [HEADS UP] wxPython 4.2.0 in Rawhide


On 8/9/22 01:09 PM, Scott Talbert wrote:

Hi,

Upstream wxPython has finally made a new release and this involves migrating to 
wxWidgets 3.2.0 at the same time.  I'm planning to build the new wxPython in 
Rawhide after F37 branch (although could put it in F37 later).

For those packages that use both wxPython and wxWidgets (I *think* this is just 
kicad?), do you want me to do this in a side-tag so we can switch the packages 
at the same time?  Or just build in rawhide and let you fix things up?


That is very good news, Scott.  The upstream KiCad devs are working on 3.2.0 
right now, as part of their efforts to support the new M1 Apple machines.

If KiCad is the only customer, I'd say there is no need to do a side-tag, 
unless that is easier for you.  I'm fine either way.

Thanks,
Steve
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Request for assistance: zfs-fuse

2022-08-09 Thread Gwyn Ciesla via devel



--- Original Message ---
On Tuesday, August 9th, 2022 at 12:06 PM, Vitaly Zaitsev via devel 
 wrote:


> On 09/08/2022 18:51, Gwyn Ciesla via devel wrote:
> 

> > zfs-fuse is FTBFS starting with f36.
> 

> 

> gcc -o cmd/mount_zfs/mount_zfs.o -c "-O2 -flto=auto -ffat-lto-objects
> -fexceptions -g -grecord-gcc-switches -pipe -Wall
> -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2
> -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1
> -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1
> -m64 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables
> -fstack-clash-protection" -pipe -Wall -std=c99 -Wno-switch -Wno-unused
> -Wno-missing-braces -Wno-parentheses -Wno-uninitialized -Wcast-align
> -fno-strict-aliasing -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT
> -DTEXT_DOMAIN=\"zfs-fuse\" -ggdb -DDEBUG -fPIC -DLINUX_AIO
> -I/usr/include/tirpc -Ilib/libuutil/include -Ilib/libnvpair/include
> -Ilib/libumem/include -Ilib/libzfscommon/include -Ilib/libzpool/include
> -Ilib/libzfs/include -Ilib/libsolcompat/include -Ilib/libavl/include
> cmd/mount_zfs/mount_zfs.c
> cc1: error: argument to '-O' should be a non-negative integer, 'g', 's',
> 'z' or 'fast'
> 

> Remove the quotes around Fedora build flags.
> 

> Correct:
> -O2 -flto=auto -ffat-lto-objects -fexceptions -g ...
> 

> Bogus:
> "-O2 -flto=auto -ffat-lto-objects -fexceptions -g ..."

Doesn't help:

+ '[' -f /usr/lib/rpm/generate-rpm-note.sh ']'
+ /usr/lib/rpm/generate-rpm-note.sh zfs-fuse 0.7.2.2-22.fc38 x86_64
+ cd zfs-fuse-0.7.2.2
+ export CCFLAGS=-O2 -flto=auto -ffat-lto-objects -fexceptions -g 
-grecord-gcc-switches -pipe -Wall -Werror=format-security 
-Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS 
-specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong 
-specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic 
-fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection
+ CCFLAGS=-O2
/var/tmp/rpm-tmp.u56vY5: line 42: export: `-flto=auto': not a valid identifier
/var/tmp/rpm-tmp.u56vY5: line 42: export: `-ffat-lto-objects': not a valid 
identifier
/var/tmp/rpm-tmp.u56vY5: line 42: export: `-fexceptions': not a valid identifier
/var/tmp/rpm-tmp.u56vY5: line 42: export: `-g': not a valid identifier
/var/tmp/rpm-tmp.u56vY5: line 42: export: `-grecord-gcc-switches': not a valid 
identifier
/var/tmp/rpm-tmp.u56vY5: line 42: export: `-pipe': not a valid identifier
/var/tmp/rpm-tmp.u56vY5: line 42: export: `-Wall': not a valid identifier
/var/tmp/rpm-tmp.u56vY5: line 42: export: `-Werror=format-security': not a 
valid identifier
/var/tmp/rpm-tmp.u56vY5: line 42: export: `-Wp,-D_FORTIFY_SOURCE=2': not a 
valid identifier
/var/tmp/rpm-tmp.u56vY5: line 42: export: `-Wp,-D_GLIBCXX_ASSERTIONS': not a 
valid identifier
/var/tmp/rpm-tmp.u56vY5: line 42: export: 
`-specs=/usr/lib/rpm/redhat/redhat-hardened-cc1': not a valid identifier
/var/tmp/rpm-tmp.u56vY5: line 42: export: `-fstack-protector-strong': not a 
valid identifier
/var/tmp/rpm-tmp.u56vY5: line 42: export: 
`-specs=/usr/lib/rpm/redhat/redhat-annobin-cc1': not a valid identifier
/var/tmp/rpm-tmp.u56vY5: line 42: export: `-m64': not a valid identifier
/var/tmp/rpm-tmp.u56vY5: line 42: export: `-mtune=generic': not a valid 
identifier
/var/tmp/rpm-tmp.u56vY5: line 42: export: `-fasynchronous-unwind-tables': not a 
valid identifier
/var/tmp/rpm-tmp.u56vY5: line 42: export: `-fstack-clash-protection': not a 
valid identifier
/var/tmp/rpm-tmp.u56vY5: line 42: export: `-fcf-protection': not a valid 
identifier
error: Bad exit status from /var/tmp/rpm-tmp.u56vY5 (%build)




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

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

[HEADS UP] wxPython 4.2.0 in Rawhide


Hi,

Upstream wxPython has finally made a new release and this involves 
migrating to wxWidgets 3.2.0 at the same time.  I'm planning to build the 
new wxPython in Rawhide after F37 branch (although could put it in F37 
later).


For those packages that use both wxPython and wxWidgets (I *think* this is 
just kicad?), do you want me to do this in a side-tag so we can switch the 
packages at the same time?  Or just build in rawhide and let you fix 
things up?


Thanks,
Scott
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Request for assistance: zfs-fuse

2022-08-09 Thread Vitaly Zaitsev via devel


On 09/08/2022 18:51, Gwyn Ciesla via devel wrote:

zfs-fuse is FTBFS starting with f36.


gcc -o cmd/mount_zfs/mount_zfs.o -c "-O2 -flto=auto -ffat-lto-objects 
-fexceptions -g -grecord-gcc-switches -pipe -Wall 
-Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 
-Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 
-fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 
-m64 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables 
-fstack-clash-protection" -pipe -Wall -std=c99 -Wno-switch -Wno-unused 
-Wno-missing-braces -Wno-parentheses -Wno-uninitialized -Wcast-align 
-fno-strict-aliasing -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT 
-DTEXT_DOMAIN=\"zfs-fuse\" -ggdb -DDEBUG -fPIC -DLINUX_AIO 
-I/usr/include/tirpc -Ilib/libuutil/include -Ilib/libnvpair/include 
-Ilib/libumem/include -Ilib/libzfscommon/include -Ilib/libzpool/include 
-Ilib/libzfs/include -Ilib/libsolcompat/include -Ilib/libavl/include 
cmd/mount_zfs/mount_zfs.c
cc1: error: argument to '-O' should be a non-negative integer, 'g', 's', 
'z' or 'fast'


Remove the quotes around Fedora build flags.

Correct:
-O2 -flto=auto -ffat-lto-objects -fexceptions -g ...

Bogus:
"-O2 -flto=auto -ffat-lto-objects -fexceptions -g ..."

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

Re: [HEADS UP] wxGTK 3.2.0 in Rawhide


On Mon, 25 Jul 2022, Scott Talbert wrote:

At long last wxWidgets 3.2.0 has been released and I'm getting it into 
Rawhide.  This comes with an soname bump (but this should be the last one as 
3.2.x should now be ABI stable).


NOTE: users of wxWidgets 3.0 (wxGTK3 package) are now strongly encouraged to 
move their packages to use wxWidgets 3.2.


As an update on this, you may have noticed, I've been submitting pull 
requests to wxGTK3 (wxWidgets 3.0) package users to move them to wxGTK 
(wxWidgets 3.2).  Most packages haven't required any changes, but I've 
been submitting patches to a few that have required changes.  My informal 
goal would be to try to retire wxGTK3 by F38.


Thanks,
Scott
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Request for assistance: zfs-fuse

2022-08-09 Thread Gwyn Ciesla via devel

Good morning!

zfs-fuse is FTBFS starting with f36.

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

I've been banging my head on it for a long time, to no avail. I can get around 
the SConstruct failure by removing some environment variables, and then I hit a 
linking issue I can't get past.

Only libguestfs and libvirt require this, other that users with ZFS 
filesystems, but I'd rather not retire it if it can be avoided.

Thanks in advance,

-- 
Gwyn Ciesla
she/her/hers
 
in your fear, seek only peace 
in your fear, seek only love
-d. bowie


Sent with Proton Mail secure email.

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

Unannounced soname bump: samba-client-libs (breaking sssd and so on), redux

2022-08-09 Thread Adam Williamson

Nearly exactly a year ago, mtasaka pointed this out:

"Hello, all:

samba is upgraded from samba-4.14.6-1.fc34 to samba-4.15.0-0.0.rc1.fc35,
Its subpackage (samba-client-libs) contains libndr.so, which did soname bump:
libndr.so.1()(64bit) -> libndr.so.2()(64bit)"

Sadly, almost the exact same thing just happened again :(

https://bodhi.fedoraproject.org/updates/FEDORA-2022-b3376c521c

that bumps samba to 4.17.0, which bumps libndr from .so.2 to
libndr.so.3, which breaks things again:

evolution-mapi-0:3.45.1-2.fc37.x86_64
freeipa-server-0:4.10.0-2.fc37.x86_64
freeipa-server-trust-ad-0:4.10.0-2.fc37.x86_64
openchange-0:2.3-41.fc37.x86_64
openchange-client-0:2.3-41.fc37.x86_64
sssd-ad-0:2.7.3-2.fc37.x86_64
sssd-common-pac-0:2.7.3-2.fc37.x86_64
sssd-ipa-0:2.7.3-2.fc37.x86_64

I will start rebuilding things. But please, folks, do not do
unannounced soname bumps, it is against policy:

https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#_rawhide

"When a proposed update contains an ABI or API change: notify a week in
advance both the devel list and maintainers directly (using the
packagename-maintain...@fedoraproject.org alias) whose packages depend
on yours to rebuild or offer to do these rebuilds for them."
-- 
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: python-m3u8: how to get %pytest working

2022-08-09 Thread Miro Hrončok


On 09. 08. 22 16:45, Martin Gansser wrote:

Hi,

how do i get %pytest on the python-m3u8 package to work ?
I have already made several attempts which fail.

%check
#%%{pytest} -vv --cov-report term-missing --cov m3u8 tests/
#%%{__python3} -m pytest tests/m3u8server.py


Hi Martin,

It would certainly be helpful if you specified:

 - What do you expect to happen?
 - What actually happens instead?


A simple approach like this:

  %check
  %pytest -vv

Makes the test run. Three tests fail because they require internet, you need to 
deselect them:


  %check
  # 3 deselected tests require internet connection
  %pytest -vv -k "not (test_load_should_ and (uri or redirect))"

If you want to make it cool, talk to upstream and add a marker that maeks the 
tests as such, then you could use simpler:


  %check
  %pytest -vv -m "not internet"



As a side note, running --cov is discouraged:

https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/#_linters




[1] https://martinkg.fedorapeople.org/Packages/test/python-m3u8-3.1.0-1.fc36


https://martinkg.fedorapeople.org/Packages/test/python-m3u8-3.1.0-1.fc36.src.rpm

--
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Process to remove "abandoned" packages?

2022-08-09 Thread Mattia Verga via devel

Il 09/08/22 13:21, Miro Hrončok ha scritto:
> On 09. 08. 22 13:06, Vít Ondruch wrote:
>> You can't retire package with provenpackager powers. If that was possible, 
>> I'd
>> probably do that.
> Actually, you can.
>
Yep, you can, but then the package will be in a "weird" state. I've
actually retired a few packages on behalf of the former maintainer, but
now the packages are retired but not orphaned and only the maintainer
can orphan them (or I should file a ticket).

BTW, it would be nice if the package list in src.fp.o could be filtered
out of retired packages so that users can focus on current owned
packages. Or, maybe, users should be able to remove themselves from
commit/collaborator rights (actually only admins can add / remove users
and groups).

Mattia

___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: fedora-create-review error message

2022-08-09 Thread Michel Alexandre Salim

On Tue, Aug 09, 2022 at 03:34:56AM +, Davide Cavalca via devel wrote:
> On Sun, 2022-08-07 at 20:27 -0500, Richard Shaw wrote:
> > I'm working on a package review for libphidget22 (rename of
> > libphidget), but after typing in my bugzilla credentials I get the
> > following:
> > 
> >  > 32000: The method 'Bug.get' is not supported without using API keys
> > and the the authentication header. See
> > https://bugzilla.redhat.com/docs/en/html/api/core/v1/general.html#authentication
> >  for details on using the 'Authorization' header. at
> > /usr/share/perl5/vendor_perl/SOAP/Lite.pm line 2855.\n">
> > 
> > Haven't seen this before, but I haven't submitted a new package in a
> > while either.
> 
> This should have been fixed in
> https://pagure.io/FedoraReview/c/7330e7f1b47986211aeb2ce1059731ec6a9a1171?branch=master
> but I don't think that's made it to a release yet.
> 
Neal's made me a comaintainer, so I'll try and cut a release this week.
Going to wait until I have some spare time so I don't accidentally make
a hash of my first release!

Best regards,

-- 
Michel Alexandre Salim
identities: https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2


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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

python-m3u8: how to get %pytest working

2022-08-09 Thread Martin Gansser

Hi,

how do i get %pytest on the python-m3u8 package to work ?
I have already made several attempts which fail.

%check
#%%{pytest} -vv --cov-report term-missing --cov m3u8 tests/
#%%{__python3} -m pytest tests/m3u8server.py

[1] https://martinkg.fedorapeople.org/Packages/test/python-m3u8-3.1.0-1.fc36

Regards
Martin
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: fedora-review of m3u8 fails

2022-08-09 Thread Martin Gansser

@Artur
Thanks, that was the solution
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2116568] perl-Digest-SHA3-1.05 is available

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



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


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2116568
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2116568] perl-Digest-SHA3-1.05 is available

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

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED
   Fixed In Version||perl-Digest-SHA3-1.05-1.fc3
   ||7




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2116568
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[rpms/perl-Digest-SHA3] PR #1: Tests


jplesnik merged a pull-request against the project: `perl-Digest-SHA3` that you 
are following.

Merged pull-request:

``
Tests
``

https://src.fedoraproject.org/rpms/perl-Digest-SHA3/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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: PSA: koji armv7hl builders locking up

2022-08-09 Thread Steve Dickson




On 8/7/22 3:49 PM, Kevin Fenzi wrote:

Or just wait... I have been checking them a few times a day and
rebooting any that are locked up.

How long do we have to wait? [1] has been stuck since
Mon, 08 Aug 2022 14:17:44 UTC

steved.

[1] https://koji.fedoraproject.org/koji/taskinfo?taskID=90612742
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Okay to %excludearch i686?

2022-08-09 Thread Richard Shaw

I'm working on updating the FreeCAD package which is quite large. It
doesn't provide libraries for other packages so is there ANY reason to
continue to build it for ANY release of Fedora at this point?

Seems like a complete waste of resources.

Thanks,
RIchard
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[EPEL-devel] Re: [new / help wanted] fence-agents-epel package

2022-08-09 Thread Alex Talaran

rhel 9 ideally.

i was starting with the fedora spec file as i didn't know about needing 
the match. it isnt clear why some of these are not included in the rhel 
package but most are. i tried to search on the fence-agents github and 
bugzilla. does the pve one for instance need something too new for rhel 9?

i only have use for the pve one at the moment, but conversation with 
carl previously here gave the idea just to include them all in case 
others can use them. i am happy to test the version on el9 and it would 
get consistent use.

On 2022-08-08 17:22, Troy Dawson wrote:

Hi Alex,
I've been looking into this some.

What distribution do you want this for?
I haven't seen anywhere in your emails saying if this is for RHEL 8 or 
RHEL 9?
The spec file you have attached is for fence-agents-4.11, which is only 
in Fedora, so that doesn't let me know either.

The major problem is that the fence-agents-pve version has to match the 
fence-agents that is in your version of RHEL.
So for RHEL8 (or compatible) it needs to be version 4.2.1.  For RHEL 9 
it needs to be 4.10.0

We need to start with the correct version of fence-agents and work from 
there.

Troy

On Wed, Jul 27, 2022 at 10:03 AM Alex Talaran > wrote:

i was able to get this built and installable if anyone wants to help
test or maintain it.
an issue exists with the man pages not being built still but im not
sure
how the makefile target works for these so they are excluded for now.

maybe some other small tweaks are still needed too since its just a
(first for me) stripped down and modified upstream spec file.

On 2022-07-20 08:47, Andrew C Aitchison wrote:
 > On Wed, 20 Jul 2022, Alex Talaran wrote:
 >
 >> i ended up with the same error with that change.
 >
 > I am sorry my suggestion did not help.
 > I don't have a Red Hat compatible machine newer that RHEL6
 > (I moved to Ubuntu for work-related reasons)
 > so I am unable to test things myself.
 >
 >> is it possible its getting confused because the dirname in the
tarball
 >> is different than the package name and looking in the wrong spot?
 >
 > The -n fence-agents-%{version} in
 >  %prep
 >  %setup -q -n fence-agents-%{version}
 > is supposed to resolve that, but that setup line might need tweaking
 > to match the contents of the tarball.
 >
 > It is old and may be somewhat dated, but my bible for rewriting
.spec
 > files was the book
 >     Maximum RPM - Taking the Red Hat Package Manager to the Limit
 > a version of which is available at
 > http://ftp.rpm.org/max-rpm/index.html

 >
 >> On 2022-07-19 23:32, Andrew C Aitchison wrote:
 >>> On Tue, 19 Jul 2022, Alex Talaran wrote:
 >>>
  per a previous thread i took a shot at cleaning up the
fence-agents
  rpm to only include the missing agents and make a new package.
i am
  having some issues with the source url and getting it to
build. the
  srpm is ok, but when i try to rebuild it into a proper rpm i
get the
  following (output truncated):

  ---
  + py39_byte_compile /usr/bin/python3

/builddir/build/BUILDROOT/fence-agents-epel-4.11.0-1.el9.x86_64/usr/share/fence
  + python_binary='env PYTHONHASHSEED=0 /usr/bin/python3'
  +

bytecode_compilation_path=/builddir/build/BUILDROOT/fence-agents-epel-4.11.0-1.el9.x86_64/usr/share/fence
  + env PYTHONHASHSEED=0 /usr/bin/python3 -s -B -m compileall -o
0 -o
  1 -s
/builddir/build/BUILDROOT/fence-agents-epel-4.11.0-1.el9.x86_64
  -p /

/builddir/build/BUILDROOT/fence-agents-epel-4.11.0-1.el9.x86_64/usr/share/fence
  Listing

'/builddir/build/BUILDROOT/fence-agents-epel-4.11.0-1.el9.x86_64/usr/share/fence'...
  Can't list

'/builddir/build/BUILDROOT/fence-agents-epel-4.11.0-1.el9.x86_64/usr/share/fence'
  + chmod 0755

/builddir/build/BUILDROOT/fence-agents-epel-4.11.0-1.el9.x86_64/usr/share/fence/fence_pve.py

/builddir/build/BUILDROOT/fence-agents-epel-4.11.0-1.el9.x86_64/usr/share/fence/fence_raritan.py

/builddir/build/BUILDROOT/fence-agents-epel-4.11.0-1.el9.x86_64/usr/share/fence/fence_rcd_serial.py

/builddir/build/BUILDROOT/fence-agents-epel-4.11.0-1.el9.x86_64/usr/share/fence/fence_virsh.py
  chmod: cannot access

'/builddir/build/BUILDROOT/fence-agents-epel-4.11.0-1.el9.x86_64/usr/share/fence/fence_pve.py':
 No such file or directory
  chmod: cannot access

'/builddir/build/BUILDROOT/fence-agents-epel-4.11.0-1.el9.x86_64/usr/share/fence/fence_raritan.py':
 No such file or directory
  chmod: cannot access

Re: fedora-review of m3u8 fails

2022-08-09 Thread Artur Frenszek-Iwicki

In the spec, you have this:
> %setup -n %{module_name}-%{version}

The error message looks like this:
> /usr/lib/rpm/rpmuncompress -x -v/builddir/build/SOURCES/m3u8-3.1.0.tar.gz
> rpmuncompress: -v/builddir/build/SOURCES/m3u8-3.1.0.tar.gz: unknown option

On first glance, this looks like a bug in the definition of the "%setup" macro.
Pretty much every packaging tutorial I've seen recommends using the "-q" option 
with "%setup",
which is the "quiet" option. "Verbose" seems like the logical opposition to 
"quiet",
so I guess what happens when you're not passing "-q" to "%setup",
is that it tries to decompress the archive verbosely by passing "-v" to 
rpmuncompress.
Except that, since there's no space between "-v" and the file name, and this 
makes
rpmuncompress try to parse "-v%{SOURCE}" as an option and fail.

A.FI.
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: fedora-review of m3u8 fails

2022-08-09 Thread Panu Matilainen


On 8/9/22 15:37, Martin Gansser wrote:

Hi,

fedora-review of m3u8 fails with the following error message:

Building target platforms: x86_64
Building for target x86_64
setting SOURCE_DATE_EPOCH=1659916800
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.g2rRRB
+ umask 022
+ cd /builddir/build/BUILD
+ cd /builddir/build/BUILD
+ rm -rf m3u8-3.1.0
+ /usr/lib/rpm/rpmuncompress -x -v/builddir/build/SOURCES/m3u8-3.1.0.tar.gz
rpmuncompress: -v/builddir/build/SOURCES/m3u8-3.1.0.tar.gz: unknown option


That's a bug in rpm 4.18 alpha [1], just update your rpm to 4.18 beta 
which is in rawhide since late June.


[1] https://bugzilla.redhat.com/show_bug.cgi?id=2079127

- Panu -
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: fedora-review of m3u8 fails

2022-08-09 Thread Mikel Olasagasti

Hau idatzi du Martin Gansser (martin.gans...@gmail.com) erabiltzaileak
(2022 abu. 9, ar. (14:37)):
>
> Hi,
>
> fedora-review of m3u8 fails with the following error message:
>
> Building target platforms: x86_64
> Building for target x86_64
> setting SOURCE_DATE_EPOCH=1659916800
> Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.g2rRRB
> + umask 022
> + cd /builddir/build/BUILD
> + cd /builddir/build/BUILD
> + rm -rf m3u8-3.1.0
> + /usr/lib/rpm/rpmuncompress -x -v/builddir/build/SOURCES/m3u8-3.1.0.tar.gz
> rpmuncompress: -v/builddir/build/SOURCES/m3u8-3.1.0.tar.gz: unknown option
> error: Bad exit status from /var/tmp/rpm-tmp.g2rRRB (%prep)

Works for me using the src.rpm + fedora-review-0.8.0-1.fc36.noarch,
there is a space between -v and /builddir/ in my case.

$ fedora-review -n python-m3u8
$ grep -A1 rpmuncompress review-python-m3u8/results/build.log
+ /usr/lib/rpm/rpmuncompress -x -v /builddir/build/SOURCES/m3u8-3.1.0.tar.gz
/usr/bin/gzip -dc  '/builddir/build/SOURCES/m3u8-3.1.0.tar.gz' |
/usr/bin/tar -xvvof -

Which version of fedora-review and mock are you using? It might be
another thing, but first thing to check.

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

[rpms/perl-Digest-SHA3] PR #1: Tests


jplesnik opened a new pull-request against the project: `perl-Digest-SHA3` that 
you are following:
``
Tests
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Digest-SHA3/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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

fedora-review of m3u8 fails

2022-08-09 Thread Martin Gansser

Hi,

fedora-review of m3u8 fails with the following error message:

Building target platforms: x86_64
Building for target x86_64
setting SOURCE_DATE_EPOCH=1659916800
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.g2rRRB
+ umask 022
+ cd /builddir/build/BUILD
+ cd /builddir/build/BUILD
+ rm -rf m3u8-3.1.0
+ /usr/lib/rpm/rpmuncompress -x -v/builddir/build/SOURCES/m3u8-3.1.0.tar.gz
rpmuncompress: -v/builddir/build/SOURCES/m3u8-3.1.0.tar.gz: unknown option
error: Bad exit status from /var/tmp/rpm-tmp.g2rRRB (%prep)
RPM build errors:

[1] 
https://martinkg.fedorapeople.org/Packages/test/python-m3u8-3.1.0-1.fc36.src.rpm

What dependency is missing  ?

Regards
Martin
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Process to remove "abandoned" packages?

2022-08-09 Thread Miro Hrončok


On 09. 08. 22 13:06, Vít Ondruch wrote:


You can't retire package with provenpackager powers. If that was possible, I'd 
probably do that.


Actually, you can.

--
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Process to remove "abandoned" packages?

2022-08-09 Thread Vít Ondruch



Dne 09. 08. 22 v 12:29 Miro Hrončok napsal(a):

On 09. 08. 22 12:20, Vít Ondruch wrote:

Hi,

I have removed last use of rubygem-memcache-client package in Fedora 
minutes ago:


https://src.fedoraproject.org/rpms/rubygem-rack/c/7490abe4066b965d222764acf0ae164788cf1721 



and I think that rubygem-memcache-client would deserve to be retired 
from Fedora, because it is deprecated upstream for ~12 years and it 
functionality replaced by rubygem-dalli.


However, if I really wanted to do this, I'd need to ask Mo, possibly 
use unresponsive maintainer policy. But that is too much hassle, so 
I'll probably leave it alone.


But I'd really love to see some process to get such packages removed 
in much easier way. E.g.:



1. Open FESCo ticket with the request request

2. Send email to Fedora devel ML to collect feedback


I'd do this, cc the maintainer. Assume they agree / don't care if they 
don't argue against it.



3. Within some timeout, make a decision based on the feedback


Use provenpacakger powers to retire the package.



You can't retire package with provenpackager powers. If that was 
possible, I'd probably do that.


And also, I really think that it would be enough to orphan the package 
and the rest of the process has been well established already.



Vít




That should follow the spirit of 
https://docs.fedoraproject.org/en-US/fesco/Who_is_allowed_to_modify_which_packages/#digest 





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

[Bug 2116569] perl-Digest-SHA-6.03 is available

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



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


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2116569
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2116568] perl-Digest-SHA3-1.05 is available

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

Jitka Plesnikova  changed:

   What|Removed |Added

 CC|jples...@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=2116568
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Process to remove "abandoned" packages?

2022-08-09 Thread Miro Hrončok

On 09. 08. 22 12:20, Vít Ondruch wrote:

Hi,

I have removed last use of rubygem-memcache-client package in Fedora minutes
ago:

https://src.fedoraproject.org/rpms/rubygem-rack/c/7490abe4066b965d222764acf0ae164788cf1721

and I think that rubygem-memcache-client would deserve to be retired from
Fedora, because it is deprecated upstream for ~12 years and it functionality
replaced by rubygem-dalli.

However, if I really wanted to do this, I'd need to ask Mo, possibly use
unresponsive maintainer policy. But that is too much hassle, so I'll probably
leave it alone.

But I'd really love to see some process to get such packages removed in much
easier way. E.g.:

1. Open FESCo ticket with the request request

2. Send email to Fedora devel ML to collect feedback

I'd do this, cc the maintainer. Assume they agree / don't care if they don't
argue against it.

3. Within some timeout, make a decision based on the feedback

Use provenpacakger powers to retire the package.

That should follow the spirit of
https://docs.fedoraproject.org/en-US/fesco/Who_is_allowed_to_modify_which_packages/#digest

--
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, report it:
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2116569] perl-Digest-SHA-6.03 is available

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



--- Comment #4 from Fedora Update System  ---
FEDORA-2022-892c34c9c8 has been submitted as an update to Fedora 35.
https://bodhi.fedoraproject.org/updates/FEDORA-2022-892c34c9c8


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2116569
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Process to remove "abandoned" packages?

2022-08-09 Thread Vít Ondruch


Hi,

I have removed last use of rubygem-memcache-client package in Fedora 
minutes ago:


https://src.fedoraproject.org/rpms/rubygem-rack/c/7490abe4066b965d222764acf0ae164788cf1721

and I think that rubygem-memcache-client would deserve to be retired 
from Fedora, because it is deprecated upstream for ~12 years and it 
functionality replaced by rubygem-dalli.


However, if I really wanted to do this, I'd need to ask Mo, possibly use 
unresponsive maintainer policy. But that is too much hassle, so I'll 
probably leave it alone.


But I'd really love to see some process to get such packages removed in 
much easier way. E.g.:



1. Open FESCo ticket with the request request

2. Send email to Fedora devel ML to collect feedback

3. Within some timeout, make a decision based on the feedback

4. Orphan package, which gives some additional time to take the package 
or even resurrect the package if it turns out to be needed.



Thoughts?


Vít



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

[Bug 2116569] perl-Digest-SHA-6.03 is available

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

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED
   Fixed In Version||perl-Digest-SHA-6.03-1.fc37




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2116569
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[rpms/perl-Digest-SHA] PR #2: Tests


jplesnik merged a pull-request against the project: `perl-Digest-SHA` that you 
are following.

Merged pull-request:

``
Tests
``

https://src.fedoraproject.org/rpms/perl-Digest-SHA/pull-request/2
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[rpms/perl-Digest-SHA] PR #2: Tests


jplesnik opened a new pull-request against the project: `perl-Digest-SHA` that 
you are following:
``
Tests
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Digest-SHA/pull-request/2
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

F37 proposal: Emacs 28 (Self-Contained Change proposal)

2022-08-09 Thread Göran Uddeborg

Hello,

My package (emacs-vm) was one of the ones that broke with the upgrade
to Emacs 28 in F36. I'm trying to get it to work again.

One of the issues is that it shows up a large number of warnings.
After some time I've now understood this is because of the new native
compilation feature. Since my package doesn't include any *.eln files
and Emacs will do the compilation on first use, and put in the home
directory. The VM package has a lot of old code that triggers
warnings. Previously those have only shown up at build time, and I
have hoped for upstreams to some day fix them. Now they will also show
up at run time, which obviously is a more annoying user experience.

That brought up a question: what should Emacs add-on packages do when
it comes to native compilation? Should they build and bundle native
code? If I understand it correctly, that would mean a new patch build
of Emacs itself would also require a rebuild of all add-on packages.
Or should we let Emacs recompile native files at run time? That would
make the recompilation at Emacs upgrades automatic, but it would on
the other hand put a copy of all used libraries in each user's home
directory.

I checked the packaging guidelines
(https://docs.fedoraproject.org/en-US/packaging-guidelines/Emacs/) but
it didn't mention anything around this as far as I could tell. (It
still talks about xemacs which has been retired from the distribution,
which tells me it hasn't been updated very recently.)

To make things worse for me, with some updates VM initially works
after issuing the warnings, but doesn't work on the second start of
Emacs, when it doesn't have to recompile the code. But that's a
different story.
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: The performance impact of various debug options on Fedora Rawhide debug kernels

2022-08-09 Thread Jelle van der Waa


On 03/08/2022 22:47, Adam Williamson wrote:

On Sun, 2022-07-24 at 10:28 +0100, Richard W.M. Jones wrote:

The current Fedora Rawhide kernels are too slow to run libguestfs
tests when doing Koji builds.  These run in a qemu VM, running the
Rawhide kernel, emulated using software virtualization (ie. TCG).
They now time out because these kernels are so slow.  Until fairly
recently they were slow but working.

I wondered if particular debug options had a greater effect on
performance, so I compiled many kernels (v5.19-rc7 from upstream)
using the baseline "no debug" config, then adding each debug option
that we use in turn, and measuring the performance using [1], using
qemu software virtualization (TCG).  The tests were run many times
with warmups discarded to get the mean and standard deviation, using
the hyperfine program[2].

The results are below, and not very conclusive, but some options do
have a very large performance impact.

NO_DEBUG is the kernel compiled with no debug options enabled (ie. the
baseline).

In the actual debug kernel I expect the slow downs to be multiplied
together.  To test that I did an extra run with all debug options
enabled (ALL_DEBUG).

CONFIG_PROVE_LOCKING, CONFIG_LOCK_STAT and CONFIG_DEBUG_LOCK_ALLOC
were present and enabled in the kernel when it was imported into git
in 2010.

CONFIG_DEBUG_WW_MUTEX_SLOWPATH was turned off in the past
(RHBZ#1114160).  It seems to have been switched on again in 2020.

CONFIG_DEBUG_KMEMLEAK seems like it was enabled in 2012.

It's also possible that an existing debug option has got slower in the
upstream kernel, that is, it's not that we've recently changed
something in Fedora.


Thanks a lot for this work, Richard! And thanks to Justin for looking
at it. I would be super appreciative of anything we can do to reduce
the performance hit here, as it is also an issue for openQA testing -
we get noticeably more test failures due to timeouts, things taking
longer than expected, or typing errors when Rawhide is on a debug
kernel.


In Cockpit we recently enabled rawhide testing on the testing farm and 
noticed similar performance issues. [1]
In comparison to Fedora 36 it takes 5 minutes longer in one test 
scenario. So it would be great to speed that up a bit!


[1] https://gitlab.com/testing-farm/general/-/issues/45
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2116569] perl-Digest-SHA-6.03 is available

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

Paul Howarth  changed:

   What|Removed |Added

   Assignee|p...@city-fan.org   |jples...@redhat.com




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2116569
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2116569] perl-Digest-SHA-6.03 is available

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



--- Comment #2 from Jitka Plesnikova  ---
Yes, I did.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2116569
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2116569] perl-Digest-SHA-6.03 is available

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



--- Comment #1 from Paul Howarth  ---
Hi Jitka, I noticed that the sources for this were already uploaded - did you
start working on this already?


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2116569
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2116569] perl-Digest-SHA-6.03 is available

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

Paul Howarth  changed:

   What|Removed |Added

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




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2116569
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2116538] perl-DBD-Pg-3.16.0 is available

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



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


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2116538
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2116641] perl-MIME-Charset-1.013 is available

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



--- Comment #2 from Upstream Release Monitoring 
 ---
the-new-hotness/release-monitoring.org's scratch build of
perl-MIME-Charset-1.013-1.fc36.src.rpm for rawhide completed
http://koji.fedoraproject.org/koji/taskinfo?taskID=90635780


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2116641
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2116641] New: perl-MIME-Charset-1.013 is available

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

Bug ID: 2116641
   Summary: perl-MIME-Charset-1.013 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-MIME-Charset
  Keywords: FutureFeature, Triaged
  Assignee: xav...@bachelot.org
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: perl-devel@lists.fedoraproject.org,
xav...@bachelot.org
  Target Milestone: ---
Classification: Fedora



Releases retrieved: 1.013
Upstream release that is considered latest: 1.013
Current version/release in rawhide: 1.012.2-18.fc37
URL: http://search.cpan.org/dist/MIME-Charset/

Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.


Based on the information from Anitya:
https://release-monitoring.org/project/3070/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/perl-MIME-Charset


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2116641
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2116641] perl-MIME-Charset-1.013 is available

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



--- Comment #1 from Upstream Release Monitoring 
 ---
Created attachment 1904423
  --> https://bugzilla.redhat.com/attachment.cgi?id=1904423=edit
Update to 1.013 (#2116641)


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2116641
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2116538] perl-DBD-Pg-3.16.0 is available