[Bug 2042270] perl-Crypt-OpenSSL-X509-1.912 is available

[bugzilla]

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



--- Comment #2 from Upstream Release Monitoring 
 ---
the-new-hotness/release-monitoring.org's scratch build of
perl-Crypt-OpenSSL-X509-1.912-1.fc34.src.rpm for rawhide failed
http://koji.fedoraproject.org/koji/taskinfo?taskID=81438439


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2042270
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2031329] Please branch and build perl-Log-Log4perl in epel9

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



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


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2031329
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2041247] perl-LWP-Online for EPEL 9

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



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


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2041247
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2042270] perl-Crypt-OpenSSL-X509-1.912 is available

[bugzilla]

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



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


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2042270
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2042270] New: perl-Crypt-OpenSSL-X509-1.912 is available

[bugzilla]

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

Bug ID: 2042270
   Summary: perl-Crypt-OpenSSL-X509-1.912 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Crypt-OpenSSL-X509
  Keywords: FutureFeature, Triaged
  Assignee: wjhns...@hardakers.net
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: perl-devel@lists.fedoraproject.org,
wjhns...@hardakers.net, xav...@bachelot.org
  Target Milestone: ---
Classification: Fedora



Latest upstream release: 1.912
Current version/release in rawhide: 1.910-2.fc36
URL: http://search.cpan.org/dist/Crypt-OpenSSL-X509/

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


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2042270
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: gcc-12.0.0-0.4.fc36 in rawhide - s390x regression ?

[Remi Collet]

Le 14/01/2022 à 15:31, Jakub Jelinek a écrit :

Hi!

gcc 12 snapshot has landed as the system compiler into rawhide today.


PHP is now FTBFS on s390x only
https://koji.fedoraproject.org/koji/taskinfo?taskID=81436437


Any help welcome,
Remi


P.S. from build.log


/builddir/build/BUILD/php-8.1.2/Zend/zend_variables.h: In function 
'ZEND_FETCH_OBJ_IS_SPEC_CONST_TMPVAR_HANDLER':
/builddir/build/BUILD/php-8.1.2/Zend/zend_variables.h:32:32: error: 
inlining failed in call to 'always_inline' 'zval_ptr_dtor_nogc': target 
specific option mismatch

   32 | static zend_always_inline void zval_ptr_dtor_nogc(zval *zval_ptr)
  |^~
In file included from 
/builddir/build/BUILD/php-8.1.2/Zend/zend_execute.c:5071:
/builddir/build/BUILD/php-8.1.2/Zend/zend_vm_execute.h:8772:9: note: 
called from here

 8772 | zval_ptr_dtor_nogc(EX_VAR(opline->op2.var));
  | ^~~
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2038286] Please branch and build perl-Search-Xapian for EPEL8 and EPEL9

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #5 from Fedora Update System  ---
FEDORA-EPEL-2022-063ad9bc13 has been pushed to the Fedora EPEL 9 testing
repository.

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

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=2038286
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2041248] perl-XML-Stream for EPEL 9

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



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

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

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=2041248
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2036510] Please branch and build perl-Config-General for EPEL-9

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #5 from Fedora Update System  ---
FEDORA-EPEL-2022-69dd4e3245 has been pushed to the Fedora EPEL 9 testing
repository.

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

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=2036510
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2038286] Please branch and build perl-Search-Xapian for EPEL8 and EPEL9

[bugzilla]

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



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

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

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=2038286
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2037658] Please branch and build perl-MouseX-Foreign for EPEL 9

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



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

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

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=2037658
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2041279] Please branch and build perl-Convert-TNEF epel9

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



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

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

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=2041279
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2041174] Please branch and build perl-Crypt-PasswdMD5 in epel9

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



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

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

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=2041174
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2041284] Please branch and build perl-Test-Manifest in epel9

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



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

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

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=2041284
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2038584] ctstream-32 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version|ctstream-32-1.fc36  |ctstream-32-1.fc36
   |ctstream-32-1.el7   |ctstream-32-1.el7
   |ctstream-32-1.fc34  |ctstream-32-1.fc34
   |ctstream-32-1.fc35  |ctstream-32-1.fc35
   ||ctstream-32-1.el8



--- Comment #15 from Fedora Update System  ---
FEDORA-EPEL-2022-2239fc59a4 has been pushed to the Fedora EPEL 8 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=2038584
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2038584] ctstream-32 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version|ctstream-32-1.fc36  |ctstream-32-1.fc36
   |ctstream-32-1.el7   |ctstream-32-1.el7
   |ctstream-32-1.fc34  |ctstream-32-1.fc34
   ||ctstream-32-1.fc35



--- Comment #14 from Fedora Update System  ---
FEDORA-2022-bd552fec84 has been pushed to the Fedora 35 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=2038584
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2038635] perl-Business-ISBN-3.007 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Resolution|--- |ERRATA
   Fixed In Version|perl-Business-ISBN-3.007-1. |perl-Business-ISBN-3.007-1.
   |fc36|fc36
   ||perl-Business-ISBN-3.007-1.
   ||fc35
 Status|ON_QA   |CLOSED
Last Closed||2022-01-19 02:10:48



--- Comment #3 from Fedora Update System  ---
FEDORA-2022-9a3fc8c751 has been pushed to the Fedora 35 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=2038635
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

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

[updates]

The following Fedora EPEL 7 Security updates need testing:
 Age  URL
   6  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-2d515d4692   
binaryen-104-1.el7
   6  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-673d6fb241   
libmetalink-0.1.3-5.el7
   4  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-4dd661d32b   
prosody-0.11.12-1.el7
   4  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-04da0327c7   
clamav-0.103.5-1.el7
   3  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-f37ca1b24a   
guacamole-server-1.4.0-1.el7
   1  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-92a697e332   
zabbix40-4.0.37-1.el7
   1  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-c99f63fce9   
zabbix50-5.0.19-1.el7


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

golang-1.16.13-1.el7
js-jquery-ui-1.13.0-1.el7
monitorix-3.14.0-1.el7
nodejs-16.13.2-2.el7

Details about builds:



 golang-1.16.13-1.el7 (FEDORA-EPEL-2022-14c15afabc)
 The Go Programming Language

Update Information:

Update to go1.16.13, copied from f35

ChangeLog:

* Tue Jan 18 2022 Dave Dykstra  - 1.16.13-1
- Update to go1.16.13, copied from f35

References:

  [ 1 ] Bug #2013628 - golang-1.16 for EPEL7
https://bugzilla.redhat.com/show_bug.cgi?id=2013628




 js-jquery-ui-1.13.0-1.el7 (FEDORA-EPEL-2022-cd2d056fd2)
 jQuery user interface

Update Information:

jQuery UI update for EPEL 7.

ChangeLog:

* Thu Nov 11 2021 Mattias Ellert  - 1.13.0-1
- Update to version 1.13.0
* Thu Jul 22 2021 Fedora Release Engineering  - 
1.12.1-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_35_Mass_Rebuild




 monitorix-3.14.0-1.el7 (FEDORA-EPEL-2022-9065800cb5)
 A free, open source, lightweight system monitoring tool

Update Information:

This new version introduces three new modules: nvme.pm, which is capable of
monitoring an unlimited number of NVM Express (NVMe) devices, the amdgpu.pm, to
monitor also an unlimited number of AMD GPU graphic cards, and nvidiagpu.pm
which can be seen as an extended version of the current module nvidia.pm, as it
comes with more detailed statistics.  The rest of new features, changes and bugs
fixed are, as always, reflected in the Changes file.

ChangeLog:

* Tue Jan 18 2022 Jordi Sanfeliu  - 3.14.0-1
- Updated to 3.14.0.

References:

  [ 1 ] Bug #2041810 - monitorix-3.14.0 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2041810




 nodejs-16.13.2-2.el7 (FEDORA-EPEL-2022-bf9c411793)
 JavaScript runtime

Update Information:

Update EPEL 7 to Node.js 16.x

ChangeLog:

* Mon Jan 17 2022 Stephen Gallagher  - 1:16.13.2-2
- Add support for building on EPEL 7
* Tue Jan 11 2022 Stephen Gallagher  - 1:16.13.2-1
- Improper handling of URI Subject Alternative Names (Medium)(CVE-2021-44531)
- Certificate Verification Bypass via String Injection (Medium)(CVE-2021-44532)
- Incorrect handling of certificate subject and issuer fields 
(Medium)(CVE-2021-44533)
- Prototype pollution via `console.table` properties (Low)(CVE-2022-21824)
* Thu Dec  2 2021 Stephen Gallagher  - 1:16.13.1-2
- Enable building for EPEL 8 modules
* Thu Dec  2 2021 Stephen Gallagher  - 1:16.13.1-1
- Update to 16.13.1
- 
https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V16.md#16.13.1
* Thu Nov 25 2021 Honza Horak  - 1:16.13.0-3
- Make sure binary node-gyp is executable
  Resolves: #2026615
* Mon Nov  1 2021 Stephen Gallagher  - 1:16.13.0-1
- Update to 16.13.0
- 
https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V16.md#16.13.0
- Add support for epel8
* Mon Oct 25 2021 Stephen Gallagher  - 

[Bug 2038584] ctstream-32 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version|ctstream-32-1.fc36  |ctstream-32-1.fc36
   |ctstream-32-1.el7   |ctstream-32-1.el7
   ||ctstream-32-1.fc34



--- Comment #13 from Fedora Update System  ---
FEDORA-2022-3b8a545c7c has been pushed to the Fedora 34 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=2038584
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2038584] ctstream-32 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ON_QA   |CLOSED
   Fixed In Version|ctstream-32-1.fc36  |ctstream-32-1.fc36
   ||ctstream-32-1.el7
 Resolution|--- |ERRATA
Last Closed||2022-01-19 01:29:43



--- Comment #12 from Fedora Update System  ---
FEDORA-EPEL-2022-ba3a353080 has been pushed to the Fedora EPEL 7 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=2038584
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2038181] Add perl-XML-Namespace in EPEL 9

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ON_QA   |CLOSED
 Resolution|--- |ERRATA
Last Closed||2022-01-19 00:52:47



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


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2038181
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2038182] Add perl-XML-NamespaceFactory to EPEL 9

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ON_QA   |CLOSED
 Resolution|--- |ERRATA
Last Closed||2022-01-19 00:52:45



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


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2038182
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2032428] perl-RDF-Trine for EPEL 9

[bugzilla]

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

Bug 2038181 Summary: Add perl-XML-Namespace in EPEL 9
https://bugzilla.redhat.com/show_bug.cgi?id=2038181

   What|Removed |Added

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




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2032428
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2038180] Add perl-XML-CommonNS to EPEL 9

[bugzilla]

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

Bug 2038182 Summary: Add perl-XML-NamespaceFactory to EPEL 9
https://bugzilla.redhat.com/show_bug.cgi?id=2038182

   What|Removed |Added

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




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2038180
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2031812] perl-Plack for EPEL 9

[bugzilla]

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

Bug 2038078 Summary: perl-HTTP-Request-AsCGI for EPEL 9
https://bugzilla.redhat.com/show_bug.cgi?id=2038078

   What|Removed |Added

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




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2031812
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Remmina orphaned and I would like to take it.

[Philip Wyett]

On Tue, 2022-01-18 at 19:41 -0500, Neal Gompa wrote:
> On Tue, Jan 18, 2022 at 7:39 PM Philip Wyett  
> wrote:
> > On Wed, 2022-01-19 at 00:26 +, bugzi...@redhat.com wrote:
> > > https://bugzilla.redhat.com/show_bug.cgi?id=2031376
> > > 
> > > Fedora Admin user for bugzilla script actions 
> > > 
> > > changed:
> > > 
> > >What|Removed |Added
> > > 
> > >Assignee|pa...@hubbitus.info 
> > > |extras-orphan@fedoraproject
> > >||.org
> > > 
> > > 
> > > 
> > > --- Comment #6 from Fedora Admin user for bugzilla script actions <
> > > fedora-admin-xml...@fedoraproject.org> ---
> > > This package has changed maintainer in Fedora. Reassigning to the new
> > > maintainer of this component.
> > > 
> > > 
> > 
> > Hi all,
> > 
> > It seems remmina has been orphaned (see above). I already package remmina 
> > personally for RHEL
> > and
> > would be happy to package and maintain it for fedora, EPEL etc.
> > 
> > I am already in the packagers group and would only need to be given access.
> > 
> 
> It looks like you are listed as the maintainer now[1]? So is there
> anything to do here?
> 
> [1]: https://src.fedoraproject.org/rpms/remmina
> 
> 
> 
> 
> --
> 真実はいつも一つ！/ Always, there's only one truth!


Hi Neal,

Yeah, I saw that too once I hit the 'Take' button. We are all good, nothing 
should need doing and I
shall now begin getting it up to date.

Regards

Phil

-- 
*** Playing the game for the games own sake. ***

WWW: https://kathenas.org

Twitter: @kathenasorg

IRC: kathenas

GPG: 724AA9B52F024C8B


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

Re: Remmina orphaned and I would like to take it.

[Philip Wyett]

On Wed, 2022-01-19 at 00:38 +, Philip Wyett wrote:
> On Wed, 2022-01-19 at 00:26 +, bugzi...@redhat.com wrote:
> > https://bugzilla.redhat.com/show_bug.cgi?id=2031376
> > 
> > Fedora Admin user for bugzilla script actions 
> >  changed:
> > 
> >What|Removed |Added
> > 
> >Assignee|pa...@hubbitus.info |extras-orphan@fedoraproject
> >||.org
> > 
> > 
> > 
> > --- Comment #6 from Fedora Admin user for bugzilla script actions <
> > fedora-admin-xml...@fedoraproject.org> ---
> > This package has changed maintainer in Fedora. Reassigning to the new
> > maintainer of this component.
> > 
> > 
> 
> Hi all,
> 
> It seems remmina has been orphaned (see above). I already package remmina 
> personally for RHEL and
> would be happy to package and maintain it for fedora, EPEL etc.
> 
> I am already in the packagers group and would only need to be given access.
> 
> Regards
> 
> Phil
> 
> 

Ok, I clicked on 'Take' and was made the maintainer on 
https://src.fedoraproject.org/rpms/remmina,
so let me start work on it then. :-)

Regards

Phil

-- 
*** Playing the game for the games own sake. ***

WWW: https://kathenas.org

Twitter: @kathenasorg

IRC: kathenas

GPG: 724AA9B52F024C8B


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

Re: Remmina orphaned and I would like to take it.

[Neal Gompa]

On Tue, Jan 18, 2022 at 7:39 PM Philip Wyett  wrote:
>
> On Wed, 2022-01-19 at 00:26 +, bugzi...@redhat.com wrote:
> > https://bugzilla.redhat.com/show_bug.cgi?id=2031376
> >
> > Fedora Admin user for bugzilla script actions 
> >  changed:
> >
> >What|Removed |Added
> > 
> >Assignee|pa...@hubbitus.info |extras-orphan@fedoraproject
> >||.org
> >
> >
> >
> > --- Comment #6 from Fedora Admin user for bugzilla script actions <
> > fedora-admin-xml...@fedoraproject.org> ---
> > This package has changed maintainer in Fedora. Reassigning to the new
> > maintainer of this component.
> >
> >
>
> Hi all,
>
> It seems remmina has been orphaned (see above). I already package remmina 
> personally for RHEL and
> would be happy to package and maintain it for fedora, EPEL etc.
>
> I am already in the packagers group and would only need to be given access.
>

It looks like you are listed as the maintainer now[1]? So is there
anything to do here?

[1]: https://src.fedoraproject.org/rpms/remmina




--
真実はいつも一つ！/ Always, there's only one truth!
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Remmina orphaned and I would like to take it.

[Philip Wyett]

On Wed, 2022-01-19 at 00:26 +, bugzi...@redhat.com wrote:
> https://bugzilla.redhat.com/show_bug.cgi?id=2031376
> 
> Fedora Admin user for bugzilla script actions 
>  changed:
> 
>What|Removed |Added
> 
>Assignee|pa...@hubbitus.info |extras-orphan@fedoraproject
>||.org
> 
> 
> 
> --- Comment #6 from Fedora Admin user for bugzilla script actions <
> fedora-admin-xml...@fedoraproject.org> ---
> This package has changed maintainer in Fedora. Reassigning to the new
> maintainer of this component.
> 
> 

Hi all,

It seems remmina has been orphaned (see above). I already package remmina 
personally for RHEL and
would be happy to package and maintain it for fedora, EPEL etc.

I am already in the packagers group and would only need to be given access.

Regards

Phil

-- 
*** Playing the game for the games own sake. ***

WWW: https://kathenas.org

Twitter: @kathenasorg

IRC: kathenas

GPG: 724AA9B52F024C8B


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

[Bug 2037243] perl-String-Similarity missing from EPEL

[bugzilla]

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

Fedora Admin user for bugzilla script actions 
 changed:

   What|Removed |Added

   Assignee|rland...@redhat.com |extras-orphan@fedoraproject
   ||.org



--- Comment #3 from Fedora Admin user for bugzilla script actions 
 ---
This package has changed maintainer in Fedora. Reassigning to the new
maintainer of this component.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2037243
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: F36 Change: Silverblue and Kinoite will have /var on its own Btrfs subvolume (Self-Contained Change proposal)

[Neal Gompa]

On Tue, Jan 18, 2022 at 3:44 PM Ben Cotton  wrote:
>
> https://fedoraproject.org/wiki/Changes/VarSubvol4SilverblueKinoite
>
> == Summary ==
> Silverblue and Kinoite: For new clean automatic (guided)
> installations, create a "var" subvolume to be mounted at /var.
>
>
> == Owner ==
> * Name: [[User:chrismurphy| Chris Murphy]]
> * Email: bugzi...@colorremedies.com
>
>
> == Detailed Description ==
> Currently, Silverblue and Kinoite mimic other Fedora desktops. There
> is a "root" subvolume mounted at `/` and a "home" subvolume mounted at
> `/home`.
>
> This proposal adds a "var" subvolume to be mounted at `/var`.
>
> The "var" subvolume will be located at the top-level of the Btrfs file
> system, along-side the "root" and "home" subvolumes. An entry in
> `/etc/fstab` will mount it at `/var` during startup.
>
>
> == Benefit to Fedora ==
>
> Users who opt into Btrfs features like snapshots and rollbacks.
>
> * By moving /var into its own subvolume, it will be excluded from
> snapshots and rollbacks of the "root" subvolume, which contains `/etc`
> and `/usr`.
> * Users will find it straightforward to rollback "root" while not
> rolling back "var": including logs, VMs, databases, flatpaks, etc.
> * The ability to snapshot only "var" and use Btrfs send/receive to
> replicate only "var" permits for an efficient way of backing up the
> variable system data.
> ** A clean install can restore the "root", therefore it doesn't
> strictly need to be backed up. Meanwhile "var" and "home" can be
> restored using snapshot replication via send/receive.
>
>
> == Scope ==
> * Proposal owners:
> ** changes to lorax and anaconda as needed so that Silverblue and
> Kinoite variants have their own installation kickstart, such that
> automatic/guided installation automatically creates "var".
> *** possible liability, determine whether the the addition of /var
> mount point for Btrfs scheme results in /var mount point for other
> schemes (and inhibit)
>
>
> == Upgrade/compatibility impact ==
> Change will not be applied to upgrades. But we can document steps to
> apply the change to existing installations.
>
>
> == How To Test ==
>
> * Do a clean installation and check `df` and `/etc/fstab` for an
> explicitly listed `/var` mount point.
>
>
> == User Experience ==
>
> * The change won't generally be noticeable to users
> * Users will see an additional `/var` mount point in /etc/fstab, and `df`
> * Some utilities, notably backup programs like borg backup, and rsync
> with -x option, will treat Btrfs subvolumes as separate file systems
> and may not descend (recursively) into them.
>
>
> == Dependencies ==
>
> * Anaconda/blivet, lorax, and possibly kickstarts
>
>
> == Contingency Plan ==
>
> * Contingency deadline: beta freeze
> * Blocks release? No
>
> == Documentation ==
> No significant documentation is planned other than this change proposal.
>
>
> == Release Notes ==
>
>

This is a nice enhancement and works fine because the rpmdb is already
on /usr with rpm-ostree. I'm not sure if Anaconda supports custom
storage configurations per type in the profiles used to define variant
configurations?


--
真実はいつも一つ！/ Always, there's only one truth!
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Question on adding a new package to fedora

[Artur Frenszek-Iwicki]

> So far there has been no action on the bug to get it reviewed.
> Does it usually take a while to get the review started?
Well, the thing is - there isn't really anyone obliged to review package 
submissions.
Almost every single review is done by volunteers, using their free time.

> Do I need to inform someone to get this going?
You can try asking people on this mailing list... like you just did! :)
Proposing a review swap is also a somewhat popular process.
The IRC channels are also a place to hang out and ask people.

> I know fedora36 is coming up. It would be good to get it into that
> but if I have missed dates it can wait for f37.
New packages don't have to wait until a new version of Fedora
comes out, they can be added to existing releases.

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

Re: Self Introduction: Malcolm Inglis (mcinglis)

[Kevin Fenzi]

On Tue, Jan 18, 2022 at 08:31:05AM +0200, Otto Urpelainen wrote:
> Thank you, this is great!
> 
> Those two seem to contradict each other:
> 
> # If you are a new packager seeking sponsorship via new package or reviews
> # please close this
> 
> and
> 
> # If you are a new packager seeking sponsorship after your new package
> submission
> # was approved, please note the link to that review and your background here
> # for sponsors to review.

Well, the first was intended to tell people to first get a package
approved before filing a ticket. Otherwise they would file the
sponsorship ticket before they even filed a review or before it's
approved and then the ticket would have to wait and clog up the tracker. 

> For the re-reviewing of orphaned packages, I opened a FESCo ticket [1] so it
> can be properly added to relevant policies, or have the decision logged that
> those should not be required.
> 
> [1]: https://pagure.io/fesco/issue/2734

ok. 

I'll comment there. 

Thanks for helping document all this better!

kevin


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

Question on adding a new package to fedora

[Philip Cameron]

I am working on getting the xtrkcad program into fedora. Using
https://docs.fedoraproject.org/en-US/package-maintainers/New_Package_Process_for_Existing_Contributors/
 
I have gotten to the point of creating a bug (2040728) for a new package review.

I am not sure how the process works going forward. So far there has been no 
action on the bug to get it reviewed. Does it usually take a while to get the 
review started? Do I need to inform someone to get this going? I am just 
looking for information on how the process works and what I need to do.

I know fedora36 is coming up. It would be good to get it into that but if I 
have missed dates it can wait for f37. I am not sure what the final date was/is 
for new packages.
Thanks!
Phil
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Big Node.js jump coming to EPEL 7

[Stephen Gallagher]

On Mon, Jan 17, 2022 at 7:21 PM Stephen Gallagher  wrote:
>
> Last week, I retired the `nodejs` package from EPEL 7 because it was
> (I believed) stuck on Node.js 6.x due to insufficient dependency
> support. Apparently, this broke a few things like uglify-js[1], so I
> spent today looking into whether I could get Node.js 16.x to work (the
> latest LTS release) and it turns out that I can indeed bludgeon it
> into working. I have a COPR[2] with a build of Node.js 16.x for EPEL 7
> available to try while I await releng unretiring[3] the package.
>
> Please note: Node.js 16.x is a SIGNIFICANT version jump. It is very
> probably that some of your Node packages may not work properly against
> it. I urge anyone who is maintaining any such packages in EPEL 7 to
> try them out against the aforementioned COPR prior to my building it
> in EPEL proper.
>
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=2041022
> [2] https://copr.fedorainfracloud.org/coprs/sgallagh/nodejs_epel7/
> [3] https://pagure.io/releng/issue/10541


This is now built and on its way to the epel-testing repository:
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-bf9c411793
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[EPEL-devel] Re: Big Node.js jump coming to EPEL 7

[Stephen Gallagher]

On Mon, Jan 17, 2022 at 7:21 PM Stephen Gallagher  wrote:
>
> Last week, I retired the `nodejs` package from EPEL 7 because it was
> (I believed) stuck on Node.js 6.x due to insufficient dependency
> support. Apparently, this broke a few things like uglify-js[1], so I
> spent today looking into whether I could get Node.js 16.x to work (the
> latest LTS release) and it turns out that I can indeed bludgeon it
> into working. I have a COPR[2] with a build of Node.js 16.x for EPEL 7
> available to try while I await releng unretiring[3] the package.
>
> Please note: Node.js 16.x is a SIGNIFICANT version jump. It is very
> probably that some of your Node packages may not work properly against
> it. I urge anyone who is maintaining any such packages in EPEL 7 to
> try them out against the aforementioned COPR prior to my building it
> in EPEL proper.
>
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=2041022
> [2] https://copr.fedorainfracloud.org/coprs/sgallagh/nodejs_epel7/
> [3] https://pagure.io/releng/issue/10541


This is now built and on its way to the epel-testing repository:
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-bf9c411793
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

F36 Change: Silverblue and Kinoite will have /var on its own Btrfs subvolume (Self-Contained Change proposal)

[Ben Cotton]

https://fedoraproject.org/wiki/Changes/VarSubvol4SilverblueKinoite

== Summary ==
Silverblue and Kinoite: For new clean automatic (guided)
installations, create a "var" subvolume to be mounted at /var.


== Owner ==
* Name: [[User:chrismurphy| Chris Murphy]]
* Email: bugzi...@colorremedies.com


== Detailed Description ==
Currently, Silverblue and Kinoite mimic other Fedora desktops. There
is a "root" subvolume mounted at `/` and a "home" subvolume mounted at
`/home`.

This proposal adds a "var" subvolume to be mounted at `/var`.

The "var" subvolume will be located at the top-level of the Btrfs file
system, along-side the "root" and "home" subvolumes. An entry in
`/etc/fstab` will mount it at `/var` during startup.


== Benefit to Fedora ==

Users who opt into Btrfs features like snapshots and rollbacks.

* By moving /var into its own subvolume, it will be excluded from
snapshots and rollbacks of the "root" subvolume, which contains `/etc`
and `/usr`.
* Users will find it straightforward to rollback "root" while not
rolling back "var": including logs, VMs, databases, flatpaks, etc.
* The ability to snapshot only "var" and use Btrfs send/receive to
replicate only "var" permits for an efficient way of backing up the
variable system data.
** A clean install can restore the "root", therefore it doesn't
strictly need to be backed up. Meanwhile "var" and "home" can be
restored using snapshot replication via send/receive.


== Scope ==
* Proposal owners:
** changes to lorax and anaconda as needed so that Silverblue and
Kinoite variants have their own installation kickstart, such that
automatic/guided installation automatically creates "var".
*** possible liability, determine whether the the addition of /var
mount point for Btrfs scheme results in /var mount point for other
schemes (and inhibit)


== Upgrade/compatibility impact ==
Change will not be applied to upgrades. But we can document steps to
apply the change to existing installations.


== How To Test ==

* Do a clean installation and check `df` and `/etc/fstab` for an
explicitly listed `/var` mount point.


== User Experience ==

* The change won't generally be noticeable to users
* Users will see an additional `/var` mount point in /etc/fstab, and `df`
* Some utilities, notably backup programs like borg backup, and rsync
with -x option, will treat Btrfs subvolumes as separate file systems
and may not descend (recursively) into them.


== Dependencies ==

* Anaconda/blivet, lorax, and possibly kickstarts


== Contingency Plan ==

* Contingency deadline: beta freeze
* Blocks release? No

== Documentation ==
No significant documentation is planned other than this change proposal.


== Release Notes ==


-- 
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

F36 Change: Silverblue and Kinoite will have /var on its own Btrfs subvolume (Self-Contained Change proposal)

[Ben Cotton]

https://fedoraproject.org/wiki/Changes/VarSubvol4SilverblueKinoite

== Summary ==
Silverblue and Kinoite: For new clean automatic (guided)
installations, create a "var" subvolume to be mounted at /var.


== Owner ==
* Name: [[User:chrismurphy| Chris Murphy]]
* Email: bugzi...@colorremedies.com


== Detailed Description ==
Currently, Silverblue and Kinoite mimic other Fedora desktops. There
is a "root" subvolume mounted at `/` and a "home" subvolume mounted at
`/home`.

This proposal adds a "var" subvolume to be mounted at `/var`.

The "var" subvolume will be located at the top-level of the Btrfs file
system, along-side the "root" and "home" subvolumes. An entry in
`/etc/fstab` will mount it at `/var` during startup.


== Benefit to Fedora ==

Users who opt into Btrfs features like snapshots and rollbacks.

* By moving /var into its own subvolume, it will be excluded from
snapshots and rollbacks of the "root" subvolume, which contains `/etc`
and `/usr`.
* Users will find it straightforward to rollback "root" while not
rolling back "var": including logs, VMs, databases, flatpaks, etc.
* The ability to snapshot only "var" and use Btrfs send/receive to
replicate only "var" permits for an efficient way of backing up the
variable system data.
** A clean install can restore the "root", therefore it doesn't
strictly need to be backed up. Meanwhile "var" and "home" can be
restored using snapshot replication via send/receive.


== Scope ==
* Proposal owners:
** changes to lorax and anaconda as needed so that Silverblue and
Kinoite variants have their own installation kickstart, such that
automatic/guided installation automatically creates "var".
*** possible liability, determine whether the the addition of /var
mount point for Btrfs scheme results in /var mount point for other
schemes (and inhibit)


== Upgrade/compatibility impact ==
Change will not be applied to upgrades. But we can document steps to
apply the change to existing installations.


== How To Test ==

* Do a clean installation and check `df` and `/etc/fstab` for an
explicitly listed `/var` mount point.


== User Experience ==

* The change won't generally be noticeable to users
* Users will see an additional `/var` mount point in /etc/fstab, and `df`
* Some utilities, notably backup programs like borg backup, and rsync
with -x option, will treat Btrfs subvolumes as separate file systems
and may not descend (recursively) into them.


== Dependencies ==

* Anaconda/blivet, lorax, and possibly kickstarts


== Contingency Plan ==

* Contingency deadline: beta freeze
* Blocks release? No

== Documentation ==
No significant documentation is planned other than this change proposal.


== Release Notes ==


-- 
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Packaging my own software?

[Stephen Gallagher]

On Tue, Jan 18, 2022 at 2:31 PM Chris Adams  wrote:
>
> I've got a script for quickly building KVM VMs with libvirt from a
> kickstart, and I think others would find this useful.  I've put it on
> Github, including an RPM spec, and would like to see it in Fedora and
> EPEL.
>
> Is it okay for me to package my own software, or should I try to recruit
> someone else?  Packaging my own software makes it feel like I'm abusing
> Fedora's infrastructure and mirror servers around the world, just to
> make it easier for me to install my own script and dependencies. :)
>
> Right now, the script is ks-libvirt, and I named my repo ks-install (so
> that's what I'd name the RPM), because I plan to take the same framework
> and make other scripts to do the same thing to other VM platforms
> (oVirt, and maybe VMware).

There's nothing wrong with maintaining your own software in Fedora. In
fact, it's highly encouraged, because that makes it more likely that
bug reports will be acted upon!
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Rawhide kernel crash

[Leigh Scott]

> On Tue, Jan 18, 2022 at 6:30 AM Leigh Scott  wrote:
> 
> Indeed it does, though kernel build is not kernel update.  It will be
> a good 2 weeks before 5.16 kernels are offered as an official update.
> The point is to get more testing on simpledrm, so I plan to keep it on
> at least through the first test week kernels to get some feedback on
> it.
> 
> Justin

It still kills the nvidia driver.

https://forums.developer.nvidia.com/t/510-39-01-on-5-16-0-kernel-green-screen/200476
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Packaging my own software?

[Blaise Pabon]

Hi Chris,

As someone who aspires to run their homelab on libvirt (I have a lot of
hardware available), I know there would be a lot of folks who would
appreciate a known-working configuration script.
I also aspire to be a Fedora packager someday and I encourage you to look
into COPR if you want to use the infrastructure, but don't want to feel
guilty about it.

Keep in mind that there is also a next gen kickstart called ignite.
I'm using that to build images on Fedora CoreOS.

-Blaise

On Tue, Jan 18, 2022 at 2:29 PM Chris Adams  wrote:

> I've got a script for quickly building KVM VMs with libvirt from a
> kickstart, and I think others would find this useful.  I've put it on
> Github, including an RPM spec, and would like to see it in Fedora and
> EPEL.
>
> Is it okay for me to package my own software, or should I try to recruit
> someone else?  Packaging my own software makes it feel like I'm abusing
> Fedora's infrastructure and mirror servers around the world, just to
> make it easier for me to install my own script and dependencies. :)
>
> Right now, the script is ks-libvirt, and I named my repo ks-install (so
> that's what I'd name the RPM), because I plan to take the same framework
> and make other scripts to do the same thing to other VM platforms
> (oVirt, and maybe VMware).
>
> --
> Chris Adams 
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
>


-- 
LinkedIn   |  Quora
  |  Github

“If you want to go fast, go alone. If you want to go far, go
together.” --African
proverb
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Packaging my own software?

[PGNet Dev]

On 1/18/22 14:29, Chris Adams wrote:

to make it easier for me to install my own script and dependencies. :)

COPR (https://docs.fedoraproject.org/en-US/infra/sysadmin_guide/copr/) exists, 
in part, to scratch that specific itch.

Moving eventually to official builds once a COPR build is humming along is 
fairly straightforward process, although it comes of course with the addition 
of specific 'official' Fedora et al packaging guidelines.



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

Re: Packaging my own software?

[Adam Williamson]

On Tue, 2022-01-18 at 13:29 -0600, Chris Adams wrote:
> I've got a script for quickly building KVM VMs with libvirt from a
> kickstart, and I think others would find this useful.  I've put it on
> Github, including an RPM spec, and would like to see it in Fedora and
> EPEL.
> 
> Is it okay for me to package my own software, or should I try to recruit
> someone else?  Packaging my own software makes it feel like I'm abusing
> Fedora's infrastructure and mirror servers around the world, just to
> make it easier for me to install my own script and dependencies. :)

If it's wrong, then I don't want to be right!
-- 
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net

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

Packaging my own software?

[Chris Adams]

I've got a script for quickly building KVM VMs with libvirt from a
kickstart, and I think others would find this useful.  I've put it on
Github, including an RPM spec, and would like to see it in Fedora and
EPEL.

Is it okay for me to package my own software, or should I try to recruit
someone else?  Packaging my own software makes it feel like I'm abusing
Fedora's infrastructure and mirror servers around the world, just to
make it easier for me to install my own script and dependencies. :)

Right now, the script is ks-libvirt, and I named my repo ks-install (so
that's what I'd name the RPM), because I plan to take the same framework
and make other scripts to do the same thing to other VM platforms
(oVirt, and maybe VMware).

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

Summary/Minutes from today's FESCo Meeting (2022-01-18)

[Miro Hrončok]

===
#fedora-meeting: FESCO (2022-01-18)
===


Meeting started by mhroncok at 18:00:01 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting/2022-01-18/fesco.2022-01-18-18.00.log.html
.



Meeting summary
---
* init process  (mhroncok, 18:00:10)

* #2711 F36 Change: Enable fs-verity in RPM   (mhroncok, 18:02:41)

* #2721 F36 Change: DIGLIM  (mhroncok, 18:17:44)
  * LINK: https://lwn.net/Articles/880263/   (robertosassu, 18:24:53)
  * LINK:
https://www.phoronix.com/scan.php?page=news_item=Fedora-DIGLIM-Proposal
(robertosassu, 18:25:41)

* #2731 F36 Change: Relocate RPM database to /usr   (mhroncok, 18:33:49)
  * AGREED: FESCo accepts that `/usr/lib/sysimage` is the de-facto
standard between distributions and approves this Change (+5,0,-3)
(mhroncok, 18:57:32)
  * https://www.freedesktop.org/software/systemd/man/file-hierarchy.html
(zbyszek, 19:03:15)

* Next week's chair  (mhroncok, 19:04:53)
  * ACTION: StephenGallagher will chair next meeting  (mhroncok,
19:06:45)

* Open Floor  (mhroncok, 19:06:54)
  * LINK:
https://src.fedoraproject.org/rpms/redhat-rpm-config/pull-request/167
— this is for F36 change.  (zbyszek, 19:08:32)

Meeting ended at 19:14:03 UTC.




Action Items

* StephenGallagher will chair next meeting




Action Items, by person
---
* StephenGallagher
  * StephenGallagher will chair next meeting
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* mhroncok (101)
* Eighth_Doctor (58)
* robertosassu (47)
* zbyszek (40)
* dcantrell (39)
* StephenGallagher (28)
* zodbot (22)
* decathorpe (14)
* nirik (13)
* cmurf[m] (13)
* tstellar (11)
* dcavalca (9)
* bcotton (2)
* dustymabe (2)
* sgallagh (0)
* mboddu (0)
* Conan_Kudo (0)
* Pharaoh_Atem (0)
* Son_Goku (0)
* King_InuYasha (0)
* Sir_Gallantmon (0)


--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2037658] Please branch and build perl-MouseX-Foreign for EPEL 9

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



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


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2037658
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2038286] Please branch and build perl-Search-Xapian for EPEL8 and EPEL9

[bugzilla]

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



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


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2038286
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2038286] Please branch and build perl-Search-Xapian for EPEL8 and EPEL9

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



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


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2038286
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: gcc-12.0.0-0.4.fc36 in rawhide

[Jakub Jelinek]

On Tue, Jan 18, 2022 at 03:13:22PM +, Sérgio Basto wrote:
> On Mon, 2022-01-17 at 14:36 +, Sérgio Basto wrote:
> > On Mon, 2022-01-17 at 15:10 +0100, Vitaly Zaitsev via devel wrote:
> > > On 17/01/2022 15:00, Ben Beasley wrote:
> > > > dependency “json”: https://github.com/nlohmann/json/issues/3138
> > > 
> > > https://bugzilla.redhat.com/show_bug.cgi?id=2041187
> > > 
> > 
> > Rawhide compose doomed again [1] :( , I still haven't the results of 
> > koschei opencv altivec build with gcc-12.0.0-0.5, it failed with gcc-
> > 12.0.0-0.4 [2] 
> > 
> 
> 
> Build with gcc-12.0.0-0.5 not fixed the error related with altivec 
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=2041573

It fixed the error related to altivec others were reporting - 
#2040825.  For the above I'd need preprocessed source + gcc command line,
can be a gcc bug, can be a package bug of using altivec incorrectly.

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

pghmcfc pushed to perl-Return-Type (epel9). "Update to 0.007 (..more)"

[notifications]

Notification time stamped 2022-01-18 16:37:58 UTC

From e29cf907e0a3385b723c0d8a50755ee32b83f550 Mon Sep 17 00:00:00 2001
From: Paul Howarth 
Date: Jan 17 2022 13:02:42 +
Subject: Update to 0.007


- New upstream release 0.007
  - Bugfix: Thing expected to be an array isn't always an array but is still a
reference
  - Added: :ReturnType(Void) shortcut

---

diff --git a/.gitignore b/.gitignore
index ab6300c..15d4784 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1 +1,2 @@
 /Return-Type-0.005.tar.gz
+/Return-Type-0.007.tar.gz
diff --git a/perl-Return-Type.spec b/perl-Return-Type.spec
index e36f07b..5f97f45 100644
--- a/perl-Return-Type.spec
+++ b/perl-Return-Type.spec
@@ -1,6 +1,6 @@
 Name:   perl-Return-Type
-Version:0.005
-Release:10%{?dist}
+Version:0.007
+Release:1%{?dist}
 Summary:Specify a return type for a function
 License:GPL+ or Artistic
 URL:https://metacpan.org/release/Return-Type
@@ -57,6 +57,12 @@ make test
 %{_mandir}/man3/Return::Type.3*
 
 %changelog
+* Mon Jan  3 2022 Paul Howarth  - 0.007-1
+- Update to 0.007
+  - Bugfix: Thing expected to be an array isn't always an array but is still a
+reference
+  - Added: :ReturnType(Void) shortcut
+
 * Thu Oct 24 2019 Paul Howarth  - 0.005-10
 - Spec tidy-up
   - Classify buildreqs by usage
diff --git a/sources b/sources
index 0f95d21..7338aa4 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (Return-Type-0.005.tar.gz) = 
3becf953b58102d771a88408e51d13158e667da98a4dcae2cf6b51cb0b90a7fb94a220a037ffcf9834ea47a47f69e756fc070d5b9a01ea5709fd9fb291701fb6
+SHA512 (Return-Type-0.007.tar.gz) = 
b99af812cfbaa18e706f410001cfe8646b1a6e71b5fd77ca2459f211620773d55129c16d0b5305b39a66050d4faeadea78507c2422ee72910c0edd99cb5c32dc



https://src.fedoraproject.org/rpms/perl-Return-Type/c/e29cf907e0a3385b723c0d8a50755ee32b83f550?branch=epel9
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

pghmcfc pushed to perl-Return-Type (epel9). "remove package.cfg per new epel-playground policy"

[notifications]

Notification time stamped 2022-01-18 16:37:58 UTC

From dd742273e8b8d8a5022a729fad2a689b8e615696 Mon Sep 17 00:00:00 2001
From: Troy Dawson 
Date: Sep 24 2020 16:26:41 +
Subject: remove package.cfg per new epel-playground policy


---

diff --git a/package.cfg b/package.cfg
deleted file mode 100644
index 66ea79d..000
--- a/package.cfg
+++ /dev/null
@@ -1,2 +0,0 @@
-[koji]
-targets = epel8 epel8-playground
\ No newline at end of file



https://src.fedoraproject.org/rpms/perl-Return-Type/c/dd742273e8b8d8a5022a729fad2a689b8e615696?branch=epel9
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

pghmcfc pushed to perl-Return-Type (epel9). "- Rebuilt for https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild (..more)"

[notifications]

Notification time stamped 2022-01-18 16:37:58 UTC

From 4f8100512a71856647915ef517ebb7f2d4e178a5 Mon Sep 17 00:00:00 2001
From: Fedora Release Engineering 
Date: Oct 25 2019 14:37:32 +
Subject: - Rebuilt for https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild


Signed-off-by: Fedora Release Engineering 

---

diff --git a/perl-Return-Type.spec b/perl-Return-Type.spec
index c70d9b7..509ae5a 100644
--- a/perl-Return-Type.spec
+++ b/perl-Return-Type.spec
@@ -1,6 +1,6 @@
 Name:   perl-Return-Type
 Version:0.005
-Release:5%{?dist}
+Release:6%{?dist}
 Summary:Specify a return type for a function
 License:GPL+ or Artistic
 URL:https://metacpan.org/release/Return-Type
@@ -56,6 +56,9 @@ library are supported.
 %{_mandir}/man3/*
 
 %changelog
+* Fri Jul 13 2018 Fedora Release Engineering  - 
0.005-6
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild
+
 * Sat Jun 30 2018 Jitka Plesnikova  - 0.005-5
 - Perl 5.28 rebuild
 



https://src.fedoraproject.org/rpms/perl-Return-Type/c/4f8100512a71856647915ef517ebb7f2d4e178a5?branch=epel9
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

pghmcfc pushed to perl-Return-Type (epel9). "Spec tidy-up (..more)"

[notifications]

Notification time stamped 2022-01-18 16:37:58 UTC

From be622f5115077f841b76b49541ecfba59d4ff1ef Mon Sep 17 00:00:00 2001
From: Paul Howarth 
Date: Oct 25 2019 14:37:32 +
Subject: Spec tidy-up


- Classify buildreqs by usage
- Use %{make_build} and %{make_install}
- Fix permissions verbosely
- Make %files list more explicit

---

diff --git a/perl-Return-Type.spec b/perl-Return-Type.spec
index 690649a..e36f07b 100644
--- a/perl-Return-Type.spec
+++ b/perl-Return-Type.spec
@@ -1,34 +1,36 @@
 Name:   perl-Return-Type
 Version:0.005
-Release:9%{?dist}
+Release:10%{?dist}
 Summary:Specify a return type for a function
 License:GPL+ or Artistic
 URL:https://metacpan.org/release/Return-Type
 Source0:
https://cpan.metacpan.org/authors/id/T/TO/TOBYINK/Return-Type-%{version}.tar.gz
 BuildArch:  noarch
-
-BuildRequires:  %{__perl}
-BuildRequires:  %{__make}
-
-BuildRequires:  perl-interpreter >= 0:5.008
+# Build
+BuildRequires:  coreutils
+BuildRequires:  make
 BuildRequires:  perl-generators
+BuildRequires:  perl-interpreter >= 0:5.008
+BuildRequires:  perl(ExtUtils::MakeMaker) >= 6.76
+# Module Runtime
 BuildRequires:  perl(Attribute::Handlers)
 BuildRequires:  perl(Eval::TypeTiny)
-BuildRequires:  perl(ExtUtils::MakeMaker) >= 6.17
+BuildRequires:  perl(strict)
 BuildRequires:  perl(Sub::Util)
-BuildRequires:  perl(Test::Fatal)
-BuildRequires:  perl(Test::More) >= 0.96
 BuildRequires:  perl(Types::Standard)
 BuildRequires:  perl(Types::TypeTiny)
-BuildRequires:  perl(strict)
 BuildRequires:  perl(warnings)
-
-# optional
+# Optional Functionality
 BuildRequires:  perl(Scope::Upper)
+# Test Suite
+BuildRequires:  perl(constant)
+BuildRequires:  perl(Test::Fatal)
+BuildRequires:  perl(Test::More) >= 0.96
+# Optional Tests
+# Dependencies
+Requires:   perl(:MODULE_COMPAT_%(eval "`perl -V:version`"; echo $version))
 Suggests:   perl(Scope::Upper)
 
-Requires:   perl(:MODULE_COMPAT_%(eval "`%{__perl} -V:version`"; echo 
$version))
-
 %description
 Return::Type allows you to specify a return type for your subs. Type
 constraints from any Type::Tiny, MooseX::Types or MouseX::Types type
@@ -38,24 +40,30 @@ library are supported.
 %setup -q -n Return-Type-%{version}
 
 %build
-%{__perl} Makefile.PL INSTALLDIRS=vendor NO_PACKLIST=1
-%{__make} %{?_smp_mflags}
+perl Makefile.PL INSTALLDIRS=vendor NO_PACKLIST=1 NO_PERLLOCAL=1
+%{make_build}
 
 %install
-%{__make} pure_install DESTDIR=$RPM_BUILD_ROOT
-
-%{_fixperms} $RPM_BUILD_ROOT/*
+%{make_install}
+%{_fixperms} -c %{buildroot}
 
 %check
-%{__make} test
+make test
 
 %files
-%doc Changes README CREDITS
 %license COPYRIGHT LICENSE
-%{perl_vendorlib}/*
-%{_mandir}/man3/*
+%doc Changes README CREDITS
+%{perl_vendorlib}/Return/
+%{_mandir}/man3/Return::Type.3*
 
 %changelog
+* Thu Oct 24 2019 Paul Howarth  - 0.005-10
+- Spec tidy-up
+  - Classify buildreqs by usage
+  - Use %%{make_build} and %%{make_install}
+  - Fix permissions verbosely
+  - Make %%files list more explicit
+
 * Fri Jul 26 2019 Fedora Release Engineering  - 
0.005-9
 - Rebuilt for https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild
 



https://src.fedoraproject.org/rpms/perl-Return-Type/c/be622f5115077f841b76b49541ecfba59d4ff1ef?branch=epel9
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

pghmcfc pushed to perl-Return-Type (epel9). "Initial Fedora package."

[notifications]

Notification time stamped 2022-01-18 16:37:58 UTC

From b6d6358c0e65abe480d74256510e2cedc34e14c3 Mon Sep 17 00:00:00 2001
From: Ralf Corsépius 
Date: Feb 10 2017 14:56:47 +
Subject: Initial Fedora package.


---

diff --git a/.gitignore b/.gitignore
index e69de29..ab6300c 100644
--- a/.gitignore
+++ b/.gitignore
@@ -0,0 +1 @@
+/Return-Type-0.005.tar.gz
diff --git a/perl-Return-Type.spec b/perl-Return-Type.spec
new file mode 100644
index 000..59a8cbc
--- /dev/null
+++ b/perl-Return-Type.spec
@@ -0,0 +1,60 @@
+Name:   perl-Return-Type
+Version:0.005
+Release:1%{?dist}
+Summary:Specify a return type for a function
+License:GPL+ or Artistic
+URL:http://search.cpan.org/dist/Return-Type/
+Source0:
http://www.cpan.org/authors/id/T/TO/TOBYINK/Return-Type-%{version}.tar.gz
+BuildArch:  noarch
+
+BuildRequires:  %{__perl}
+BuildRequires:  %{__make}
+
+BuildRequires:  perl >= 0:5.008
+BuildRequires:  perl-generators
+BuildRequires:  perl(Attribute::Handlers)
+BuildRequires:  perl(Eval::TypeTiny)
+BuildRequires:  perl(ExtUtils::MakeMaker) >= 6.17
+BuildRequires:  perl(Sub::Util)
+BuildRequires:  perl(Test::Fatal)
+BuildRequires:  perl(Test::More) >= 0.96
+BuildRequires:  perl(Types::Standard)
+BuildRequires:  perl(Types::TypeTiny)
+BuildRequires:  perl(strict)
+BuildRequires:  perl(warnings)
+
+# optional
+BuildRequires:  perl(Scope::Upper)
+Suggests:   perl(Scope::Upper)
+
+Requires:   perl(:MODULE_COMPAT_%(eval "`%{__perl} -V:version`"; echo 
$version))
+
+%description
+Return::Type allows you to specify a return type for your subs. Type
+constraints from any Type::Tiny, MooseX::Types or MouseX::Types type
+library are supported.
+
+%prep
+%setup -q -n Return-Type-%{version}
+
+%build
+%{__perl} Makefile.PL INSTALLDIRS=vendor NO_PACKLIST=1
+%{__make} %{?_smp_mflags}
+
+%install
+%{__make} pure_install DESTDIR=$RPM_BUILD_ROOT
+
+%{_fixperms} $RPM_BUILD_ROOT/*
+
+%check
+%{__make} test
+
+%files
+%doc Changes README CREDITS
+%license COPYRIGHT LICENSE
+%{perl_vendorlib}/*
+%{_mandir}/man3/*
+
+%changelog
+* Thu Feb 02 2017 Ralf Corsépius  - 0.005-1
+- Initial Fedora package.
diff --git a/sources b/sources
index e69de29..0f95d21 100644
--- a/sources
+++ b/sources
@@ -0,0 +1 @@
+SHA512 (Return-Type-0.005.tar.gz) = 
3becf953b58102d771a88408e51d13158e667da98a4dcae2cf6b51cb0b90a7fb94a220a037ffcf9834ea47a47f69e756fc070d5b9a01ea5709fd9fb291701fb6



https://src.fedoraproject.org/rpms/perl-Return-Type/c/b6d6358c0e65abe480d74256510e2cedc34e14c3?branch=epel9
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

pghmcfc pushed to perl-Return-Type (epel9). "- Rebuilt for https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild (..more)"

[notifications]

Notification time stamped 2022-01-18 16:37:58 UTC

From d86293b910aed11c12d7fd69a534e715eb58cfbf Mon Sep 17 00:00:00 2001
From: Fedora Release Engineering 
Date: Oct 25 2019 14:37:32 +
Subject: - Rebuilt for https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild


Signed-off-by: Fedora Release Engineering 

---

diff --git a/perl-Return-Type.spec b/perl-Return-Type.spec
index b6dbb9f..690649a 100644
--- a/perl-Return-Type.spec
+++ b/perl-Return-Type.spec
@@ -1,6 +1,6 @@
 Name:   perl-Return-Type
 Version:0.005
-Release:8%{?dist}
+Release:9%{?dist}
 Summary:Specify a return type for a function
 License:GPL+ or Artistic
 URL:https://metacpan.org/release/Return-Type
@@ -56,6 +56,9 @@ library are supported.
 %{_mandir}/man3/*
 
 %changelog
+* Fri Jul 26 2019 Fedora Release Engineering  - 
0.005-9
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild
+
 * Fri May 31 2019 Jitka Plesnikova  - 0.005-8
 - Perl 5.30 rebuild
 



https://src.fedoraproject.org/rpms/perl-Return-Type/c/d86293b910aed11c12d7fd69a534e715eb58cfbf?branch=epel9
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

pghmcfc pushed to perl-Return-Type (epel9). "cpan.org addresses moved to MetaCPAN "

[notifications]

Notification time stamped 2022-01-18 16:37:58 UTC

From 61d2f9fcf10c10df5318c8b437d16e103727302e Mon Sep 17 00:00:00 2001
From: Petr Písař 
Date: Oct 25 2019 14:37:31 +
Subject: cpan.org addresses moved to MetaCPAN 



---

diff --git a/perl-Return-Type.spec b/perl-Return-Type.spec
index 39903cf..de4b1e4 100644
--- a/perl-Return-Type.spec
+++ b/perl-Return-Type.spec
@@ -3,8 +3,8 @@ Version:0.005
 Release:4%{?dist}
 Summary:Specify a return type for a function
 License:GPL+ or Artistic
-URL:http://search.cpan.org/dist/Return-Type/
-Source0:
http://www.cpan.org/authors/id/T/TO/TOBYINK/Return-Type-%{version}.tar.gz
+URL:https://metacpan.org/release/Return-Type
+Source0:
https://cpan.metacpan.org/authors/id/T/TO/TOBYINK/Return-Type-%{version}.tar.gz
 BuildArch:  noarch
 
 BuildRequires:  %{__perl}



https://src.fedoraproject.org/rpms/perl-Return-Type/c/61d2f9fcf10c10df5318c8b437d16e103727302e?branch=epel9
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

pghmcfc pushed to perl-Return-Type (epel9). "Perl 5.30 rebuild"

[notifications]

Notification time stamped 2022-01-18 16:37:58 UTC

From 35c39bff0fdd7be292e2b9cdd96ca83b32e749cb Mon Sep 17 00:00:00 2001
From: Jitka Plesnikova 
Date: Oct 25 2019 14:37:32 +
Subject: Perl 5.30 rebuild


---

diff --git a/perl-Return-Type.spec b/perl-Return-Type.spec
index 06d16ef..b6dbb9f 100644
--- a/perl-Return-Type.spec
+++ b/perl-Return-Type.spec
@@ -1,6 +1,6 @@
 Name:   perl-Return-Type
 Version:0.005
-Release:7%{?dist}
+Release:8%{?dist}
 Summary:Specify a return type for a function
 License:GPL+ or Artistic
 URL:https://metacpan.org/release/Return-Type
@@ -56,6 +56,9 @@ library are supported.
 %{_mandir}/man3/*
 
 %changelog
+* Fri May 31 2019 Jitka Plesnikova  - 0.005-8
+- Perl 5.30 rebuild
+
 * Fri Feb 01 2019 Fedora Release Engineering  - 
0.005-7
 - Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild
 



https://src.fedoraproject.org/rpms/perl-Return-Type/c/35c39bff0fdd7be292e2b9cdd96ca83b32e749cb?branch=epel9
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

pghmcfc pushed to perl-Return-Type (epel9). "- Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild (..more)"

[notifications]

Notification time stamped 2022-01-18 16:37:58 UTC

From 7d8f5d4244d79aa0e3b47573686769fd2e4ba54e Mon Sep 17 00:00:00 2001
From: Fedora Release Engineering 
Date: Oct 25 2019 14:37:32 +
Subject: - Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild


Signed-off-by: Fedora Release Engineering 

---

diff --git a/perl-Return-Type.spec b/perl-Return-Type.spec
index 509ae5a..06d16ef 100644
--- a/perl-Return-Type.spec
+++ b/perl-Return-Type.spec
@@ -1,6 +1,6 @@
 Name:   perl-Return-Type
 Version:0.005
-Release:6%{?dist}
+Release:7%{?dist}
 Summary:Specify a return type for a function
 License:GPL+ or Artistic
 URL:https://metacpan.org/release/Return-Type
@@ -56,6 +56,9 @@ library are supported.
 %{_mandir}/man3/*
 
 %changelog
+* Fri Feb 01 2019 Fedora Release Engineering  - 
0.005-7
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild
+
 * Fri Jul 13 2018 Fedora Release Engineering  - 
0.005-6
 - Rebuilt for https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild
 



https://src.fedoraproject.org/rpms/perl-Return-Type/c/7d8f5d4244d79aa0e3b47573686769fd2e4ba54e?branch=epel9
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

pghmcfc pushed to perl-Return-Type (epel9). "Merge remote-tracking branch 'origin/f28' into epel8"

[notifications]

Notification time stamped 2022-01-18 16:37:58 UTC

From 8fa5b57fcc452430d1bfa252055ea1687f196bf5 Mon Sep 17 00:00:00 2001
From: Paul Howarth 
Date: Oct 25 2019 14:37:18 +
Subject: Merge remote-tracking branch 'origin/f28' into epel8


---

diff --git a/.gitignore b/.gitignore
index e69de29..ab6300c 100644
--- a/.gitignore
+++ b/.gitignore
@@ -0,0 +1 @@
+/Return-Type-0.005.tar.gz
diff --git a/perl-Return-Type.spec b/perl-Return-Type.spec
new file mode 100644
index 000..39903cf
--- /dev/null
+++ b/perl-Return-Type.spec
@@ -0,0 +1,69 @@
+Name:   perl-Return-Type
+Version:0.005
+Release:4%{?dist}
+Summary:Specify a return type for a function
+License:GPL+ or Artistic
+URL:http://search.cpan.org/dist/Return-Type/
+Source0:
http://www.cpan.org/authors/id/T/TO/TOBYINK/Return-Type-%{version}.tar.gz
+BuildArch:  noarch
+
+BuildRequires:  %{__perl}
+BuildRequires:  %{__make}
+
+BuildRequires:  perl-interpreter >= 0:5.008
+BuildRequires:  perl-generators
+BuildRequires:  perl(Attribute::Handlers)
+BuildRequires:  perl(Eval::TypeTiny)
+BuildRequires:  perl(ExtUtils::MakeMaker) >= 6.17
+BuildRequires:  perl(Sub::Util)
+BuildRequires:  perl(Test::Fatal)
+BuildRequires:  perl(Test::More) >= 0.96
+BuildRequires:  perl(Types::Standard)
+BuildRequires:  perl(Types::TypeTiny)
+BuildRequires:  perl(strict)
+BuildRequires:  perl(warnings)
+
+# optional
+BuildRequires:  perl(Scope::Upper)
+Suggests:   perl(Scope::Upper)
+
+Requires:   perl(:MODULE_COMPAT_%(eval "`%{__perl} -V:version`"; echo 
$version))
+
+%description
+Return::Type allows you to specify a return type for your subs. Type
+constraints from any Type::Tiny, MooseX::Types or MouseX::Types type
+library are supported.
+
+%prep
+%setup -q -n Return-Type-%{version}
+
+%build
+%{__perl} Makefile.PL INSTALLDIRS=vendor NO_PACKLIST=1
+%{__make} %{?_smp_mflags}
+
+%install
+%{__make} pure_install DESTDIR=$RPM_BUILD_ROOT
+
+%{_fixperms} $RPM_BUILD_ROOT/*
+
+%check
+%{__make} test
+
+%files
+%doc Changes README CREDITS
+%license COPYRIGHT LICENSE
+%{perl_vendorlib}/*
+%{_mandir}/man3/*
+
+%changelog
+* Fri Feb 09 2018 Fedora Release Engineering  - 
0.005-4
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild
+
+* Thu Jul 27 2017 Fedora Release Engineering  - 
0.005-3
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_27_Mass_Rebuild
+
+* Tue Jun 06 2017 Jitka Plesnikova  - 0.005-2
+- Perl 5.26 rebuild
+
+* Thu Feb 02 2017 Ralf Corsépius  - 0.005-1
+- Initial Fedora package.
diff --git a/sources b/sources
index e69de29..0f95d21 100644
--- a/sources
+++ b/sources
@@ -0,0 +1 @@
+SHA512 (Return-Type-0.005.tar.gz) = 
3becf953b58102d771a88408e51d13158e667da98a4dcae2cf6b51cb0b90a7fb94a220a037ffcf9834ea47a47f69e756fc070d5b9a01ea5709fd9fb291701fb6



https://src.fedoraproject.org/rpms/perl-Return-Type/c/8fa5b57fcc452430d1bfa252055ea1687f196bf5?branch=epel9
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

pghmcfc pushed to perl-Return-Type (epel9). ""Adding package.cfg file""

[notifications]

Notification time stamped 2022-01-18 16:37:58 UTC

From 2b62bd3e97430c52aaaf0d9223a769b79e2f353b Mon Sep 17 00:00:00 2001
From: Gwyn Ciesla 
Date: Oct 25 2019 13:27:43 +
Subject: "Adding package.cfg file"


---

diff --git a/package.cfg b/package.cfg
new file mode 100644
index 000..66ea79d
--- /dev/null
+++ b/package.cfg
@@ -0,0 +1,2 @@
+[koji]
+targets = epel8 epel8-playground
\ No newline at end of file



https://src.fedoraproject.org/rpms/perl-Return-Type/c/2b62bd3e97430c52aaaf0d9223a769b79e2f353b?branch=epel9
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

pghmcfc pushed to perl-Return-Type (epel9). "Perl 5.28 rebuild"

[notifications]

Notification time stamped 2022-01-18 16:37:58 UTC

From 30ef46f0a25397a5966f9ea6a9349b4cff735c7f Mon Sep 17 00:00:00 2001
From: Jitka Plesnikova 
Date: Oct 25 2019 14:37:31 +
Subject: Perl 5.28 rebuild


---

diff --git a/perl-Return-Type.spec b/perl-Return-Type.spec
index de4b1e4..c70d9b7 100644
--- a/perl-Return-Type.spec
+++ b/perl-Return-Type.spec
@@ -1,6 +1,6 @@
 Name:   perl-Return-Type
 Version:0.005
-Release:4%{?dist}
+Release:5%{?dist}
 Summary:Specify a return type for a function
 License:GPL+ or Artistic
 URL:https://metacpan.org/release/Return-Type
@@ -56,6 +56,9 @@ library are supported.
 %{_mandir}/man3/*
 
 %changelog
+* Sat Jun 30 2018 Jitka Plesnikova  - 0.005-5
+- Perl 5.28 rebuild
+
 * Fri Feb 09 2018 Fedora Release Engineering  - 
0.005-4
 - Rebuilt for https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild
 



https://src.fedoraproject.org/rpms/perl-Return-Type/c/30ef46f0a25397a5966f9ea6a9349b4cff735c7f?branch=epel9
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

pghmcfc pushed to perl-Return-Type (epel9). "perl dependency renamed to perl-interpreter "

[notifications]

Notification time stamped 2022-01-18 16:37:58 UTC

From acefbc1087fd83266bdfef4db57e16b4c06fd0a3 Mon Sep 17 00:00:00 2001
From: Petr Písař 
Date: Jul 12 2017 12:05:25 +
Subject: perl dependency renamed to perl-interpreter 



---

diff --git a/perl-Return-Type.spec b/perl-Return-Type.spec
index 10f0456..242a02e 100644
--- a/perl-Return-Type.spec
+++ b/perl-Return-Type.spec
@@ -10,7 +10,7 @@ BuildArch:  noarch
 BuildRequires:  %{__perl}
 BuildRequires:  %{__make}
 
-BuildRequires:  perl >= 0:5.008
+BuildRequires:  perl-interpreter >= 0:5.008
 BuildRequires:  perl-generators
 BuildRequires:  perl(Attribute::Handlers)
 BuildRequires:  perl(Eval::TypeTiny)



https://src.fedoraproject.org/rpms/perl-Return-Type/c/acefbc1087fd83266bdfef4db57e16b4c06fd0a3?branch=epel9
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

pghmcfc pushed to perl-Return-Type (epel9). "- Rebuilt for https://fedoraproject.org/wiki/Fedora_27_Mass_Rebuild"

[notifications]

Notification time stamped 2022-01-18 16:37:58 UTC

From 94d266e8bc4687311078d52c33f3dc9a8276b636 Mon Sep 17 00:00:00 2001
From: Fedora Release Engineering 
Date: Jul 27 2017 05:57:31 +
Subject: - Rebuilt for https://fedoraproject.org/wiki/Fedora_27_Mass_Rebuild


---

diff --git a/perl-Return-Type.spec b/perl-Return-Type.spec
index 242a02e..bcba1db 100644
--- a/perl-Return-Type.spec
+++ b/perl-Return-Type.spec
@@ -1,6 +1,6 @@
 Name:   perl-Return-Type
 Version:0.005
-Release:2%{?dist}
+Release:3%{?dist}
 Summary:Specify a return type for a function
 License:GPL+ or Artistic
 URL:http://search.cpan.org/dist/Return-Type/
@@ -56,6 +56,9 @@ library are supported.
 %{_mandir}/man3/*
 
 %changelog
+* Thu Jul 27 2017 Fedora Release Engineering  - 
0.005-3
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_27_Mass_Rebuild
+
 * Tue Jun 06 2017 Jitka Plesnikova  - 0.005-2
 - Perl 5.26 rebuild
 



https://src.fedoraproject.org/rpms/perl-Return-Type/c/94d266e8bc4687311078d52c33f3dc9a8276b636?branch=epel9
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

pghmcfc pushed to perl-Return-Type (epel9). "- Rebuilt for https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild (..more)"

[notifications]

Notification time stamped 2022-01-18 16:37:58 UTC

From 087f1b639fba33eb78082362367e4d6e8f3bd9bd Mon Sep 17 00:00:00 2001
From: Fedora Release Engineering 
Date: Feb 09 2018 00:27:02 +
Subject: - Rebuilt for https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild


Signed-off-by: Fedora Release Engineering 

---

diff --git a/perl-Return-Type.spec b/perl-Return-Type.spec
index bcba1db..39903cf 100644
--- a/perl-Return-Type.spec
+++ b/perl-Return-Type.spec
@@ -1,6 +1,6 @@
 Name:   perl-Return-Type
 Version:0.005
-Release:3%{?dist}
+Release:4%{?dist}
 Summary:Specify a return type for a function
 License:GPL+ or Artistic
 URL:http://search.cpan.org/dist/Return-Type/
@@ -56,6 +56,9 @@ library are supported.
 %{_mandir}/man3/*
 
 %changelog
+* Fri Feb 09 2018 Fedora Release Engineering  - 
0.005-4
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild
+
 * Thu Jul 27 2017 Fedora Release Engineering  - 
0.005-3
 - Rebuilt for https://fedoraproject.org/wiki/Fedora_27_Mass_Rebuild
 



https://src.fedoraproject.org/rpms/perl-Return-Type/c/087f1b639fba33eb78082362367e4d6e8f3bd9bd?branch=epel9
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

pghmcfc pushed to perl-Return-Type (epel9). "Perl 5.26 rebuild"

[notifications]

Notification time stamped 2022-01-18 16:37:58 UTC

From 96ca04eba72ce8fa16df78db5249527c964595b6 Mon Sep 17 00:00:00 2001
From: Jitka Plesnikova 
Date: Jun 06 2017 19:58:19 +
Subject: Perl 5.26 rebuild


---

diff --git a/perl-Return-Type.spec b/perl-Return-Type.spec
index 59a8cbc..10f0456 100644
--- a/perl-Return-Type.spec
+++ b/perl-Return-Type.spec
@@ -1,6 +1,6 @@
 Name:   perl-Return-Type
 Version:0.005
-Release:1%{?dist}
+Release:2%{?dist}
 Summary:Specify a return type for a function
 License:GPL+ or Artistic
 URL:http://search.cpan.org/dist/Return-Type/
@@ -56,5 +56,8 @@ library are supported.
 %{_mandir}/man3/*
 
 %changelog
+* Tue Jun 06 2017 Jitka Plesnikova  - 0.005-2
+- Perl 5.26 rebuild
+
 * Thu Feb 02 2017 Ralf Corsépius  - 0.005-1
 - Initial Fedora package.



https://src.fedoraproject.org/rpms/perl-Return-Type/c/96ca04eba72ce8fa16df78db5249527c964595b6?branch=epel9
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: gcc-12.0.0-0.4.fc36 in rawhide

[Jakub Jelinek]

On Tue, Jan 18, 2022 at 07:22:00PM +0100, Florian Weimer wrote:
> >> On aarch64 I actually got a slightly different error message:
> >> 
> >>  ld: criu/pie/restorer.o: in function `lsm_set_label':
> >>  /drone/src/criu/pie/restorer.c:174: undefined reference to `strlen'
> >> 
> >> Line 174 is: "for (len = 0; label[len]; len++)"
> >> 
> >> Although there is no direct use of strlen(), it seems GCC 12 uses
> >> strlen() for that line which did not happen with GCC 11. Using
> >> '-ffreestanding' makes the compilation work with GCC 12 and CI still
> >> looks happy. Thanks.
> >
> > https://gcc.gnu.org/r12-4283-g6f966f06146be76
> > Note, gcc has been doing something similar for years for memcpy and memset.
> > -fno-tree-loop-distribute-patterns
> > will work too.
> 
> Shouldn't it be -ffreestanding?

-ffreestanding works too.  Both of these options disable the pattern
matching, -fno-tree-loop-distribute-patterns is a targetted option that
disables just these kind of optimizations, -ffreestanding has various
further effects, it implies -fno-builtin, changes some preprocessor macros
and generally will disable far more optimizations than
-fno-tree-loop-distribute-patterns will.

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

Re: gcc-12.0.0-0.4.fc36 in rawhide

[Florian Weimer]

* Jakub Jelinek:

> On Tue, Jan 18, 2022 at 07:08:00PM +0100, Adrian Reber wrote:
>> On Tue, Jan 18, 2022 at 05:56:45PM +0100, Jakub Jelinek wrote:
>> > On Tue, Jan 18, 2022 at 05:40:31PM +0100, Adrian Reber wrote:
>> > > > If there are bugs on the compiler side, please let me know immediately,
>> > > > so that those bugs can be fixed before the mass rebuild next week.
>> > > 
>> > > Not sure if it is a bug, CRIU no longer works with GCC 12.
>> > > 
>> > > CRIU creates something called 'parasite code' which is injected into
>> > > running processes for checkpointing and that part is built with
>> > > '-nostdlib'. Starting with GCC 12 we see 'strlen()' being pulled into
>> > > the parasite code which it wasn't with GCC 11.
>> > 
>> > strlen is a standard C function, so I don't see any bug in that being used
>> > unless you do a freestanding compilation (-nostdlib isn't that).
>> > If you mail me preprocessed source of handle-elf-host.c + gcc
>> > command line used to compile it, I can have a look what exactly changed.
>> 
>> Thanks for mentioning freestanding compilations. That seems to have been
>> the problem.
>> 
>> On aarch64 I actually got a slightly different error message:
>> 
>>  ld: criu/pie/restorer.o: in function `lsm_set_label':
>>  /drone/src/criu/pie/restorer.c:174: undefined reference to `strlen'
>> 
>> Line 174 is: "for (len = 0; label[len]; len++)"
>> 
>> Although there is no direct use of strlen(), it seems GCC 12 uses
>> strlen() for that line which did not happen with GCC 11. Using
>> '-ffreestanding' makes the compilation work with GCC 12 and CI still
>> looks happy. Thanks.
>
> https://gcc.gnu.org/r12-4283-g6f966f06146be76
> Note, gcc has been doing something similar for years for memcpy and memset.
> -fno-tree-loop-distribute-patterns
> will work too.

Shouldn't it be -ffreestanding?

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

Re: gcc-12.0.0-0.4.fc36 in rawhide

[Jakub Jelinek]

On Tue, Jan 18, 2022 at 07:08:00PM +0100, Adrian Reber wrote:
> On Tue, Jan 18, 2022 at 05:56:45PM +0100, Jakub Jelinek wrote:
> > On Tue, Jan 18, 2022 at 05:40:31PM +0100, Adrian Reber wrote:
> > > > If there are bugs on the compiler side, please let me know immediately,
> > > > so that those bugs can be fixed before the mass rebuild next week.
> > > 
> > > Not sure if it is a bug, CRIU no longer works with GCC 12.
> > > 
> > > CRIU creates something called 'parasite code' which is injected into
> > > running processes for checkpointing and that part is built with
> > > '-nostdlib'. Starting with GCC 12 we see 'strlen()' being pulled into
> > > the parasite code which it wasn't with GCC 11.
> > 
> > strlen is a standard C function, so I don't see any bug in that being used
> > unless you do a freestanding compilation (-nostdlib isn't that).
> > If you mail me preprocessed source of handle-elf-host.c + gcc
> > command line used to compile it, I can have a look what exactly changed.
> 
> Thanks for mentioning freestanding compilations. That seems to have been
> the problem.
> 
> On aarch64 I actually got a slightly different error message:
> 
>  ld: criu/pie/restorer.o: in function `lsm_set_label':
>  /drone/src/criu/pie/restorer.c:174: undefined reference to `strlen'
> 
> Line 174 is: "for (len = 0; label[len]; len++)"
> 
> Although there is no direct use of strlen(), it seems GCC 12 uses
> strlen() for that line which did not happen with GCC 11. Using
> '-ffreestanding' makes the compilation work with GCC 12 and CI still
> looks happy. Thanks.

https://gcc.gnu.org/r12-4283-g6f966f06146be76
Note, gcc has been doing something similar for years for memcpy and memset.
-fno-tree-loop-distribute-patterns
will work too.

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

Re: gcc-12.0.0-0.4.fc36 in rawhide

[Artur Frenszek-Iwicki]

I pulled a Rawhide container and tried building there via "fedpkg local".
When I took the g++ command line and replaced "-flto=auto -ffat-lto-objects"
with "-flto=none", the file was compiled without errors.

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

Re: gcc-12.0.0-0.4.fc36 in rawhide

[Adrian Reber]

On Tue, Jan 18, 2022 at 05:56:45PM +0100, Jakub Jelinek wrote:
> On Tue, Jan 18, 2022 at 05:40:31PM +0100, Adrian Reber wrote:
> > > If there are bugs on the compiler side, please let me know immediately,
> > > so that those bugs can be fixed before the mass rebuild next week.
> > 
> > Not sure if it is a bug, CRIU no longer works with GCC 12.
> > 
> > CRIU creates something called 'parasite code' which is injected into
> > running processes for checkpointing and that part is built with
> > '-nostdlib'. Starting with GCC 12 we see 'strlen()' being pulled into
> > the parasite code which it wasn't with GCC 11.
> 
> strlen is a standard C function, so I don't see any bug in that being used
> unless you do a freestanding compilation (-nostdlib isn't that).
> If you mail me preprocessed source of handle-elf-host.c + gcc
> command line used to compile it, I can have a look what exactly changed.

Thanks for mentioning freestanding compilations. That seems to have been
the problem.

On aarch64 I actually got a slightly different error message:

 ld: criu/pie/restorer.o: in function `lsm_set_label':
 /drone/src/criu/pie/restorer.c:174: undefined reference to `strlen'

Line 174 is: "for (len = 0; label[len]; len++)"

Although there is no direct use of strlen(), it seems GCC 12 uses
strlen() for that line which did not happen with GCC 11. Using
'-ffreestanding' makes the compilation work with GCC 12 and CI still
looks happy. Thanks.

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

Re: F36 Change: Authselect: Move State Files to /etc (Self-Contained Change proposal)

[Vitaly Zaitsev via devel]

On 18/01/2022 18:32, Ben Cotton wrote:

Authselect state files moved from/var/lib/authselect to /etc/authselect/.state.


Why /etc/authselect/.state and not /etc/authselect/state? Dot in front 
of the name means hidden file/directory.


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

F36 Change: Authselect: Move State Files to /etc (Self-Contained Change proposal)

[Ben Cotton]

https://fedoraproject.org/wiki/Changes/Authselect_Move_State_Files_To_Etc


== Summary ==

Authselect will move several files that are currently stored at
/var/lib/authselect to /etc/authselect/.state. This does not affect
configuration backup, that will be kept at
/var/lib/authselect/backups.

The files that will be moved are:
* /var/lib/authselect/dconf-db -> /etc/authselect/.state/dconf-db
* /var/lib/authselect/dconf-locks /etc/authselect/.state/dconf-locks
* /var/lib/authselect/fingerprint-auth /etc/authselect/.state/fingerprint-auth
* /var/lib/authselect/nsswitch.conf /etc/authselect/.state/nsswitch.conf
* /var/lib/authselect/password-auth /etc/authselect/.state/password-auth
* /var/lib/authselect/postlogin /etc/authselect/.state/postlogin
* /var/lib/authselect/smartcard-auth /etc/authselect/.state/smartcard-auth
* /var/lib/authselect/system-auth /etc/authselect/.state/system-auth

== Owner ==
* Name: [[User:pbrezina| Pavel Březina]]
* Email: pbrez...@redhat.com


== Detailed Description ==

These files are used by authselect to detect changes to the system
nsswitch and PAM configurations when the configuration is updated with
an updated profile using 'authselect apply-changes'. There are two
reasons for the move:

1. The current location conflicts with ostree model where /var is not
writable during rpm transaction and this currently blocks compose of
ostree systems. [https://bugzilla.redhat.com/show_bug.cgi?id=2034360
BZ#2034360]

2. Removing these files would reduce authselect functionality, user
would need to run 'authselect select --force' to restore it. Since
/var should contain only files that can be safely removed, /etc is a
better place for them.

== Feedback ==

This change is accepted by ostree system maintainers, see
[https://bugzilla.redhat.com/show_bug.cgi?id=2034360 BZ#2034360].


== Benefit to Fedora ==
This makes authselect more compatible with ostree model.

== Scope ==
* Proposal owners: Build authselect with
--statedir=/etc/authselect/.state and move files from
/var/lib/authselect to the new location. Spec file changes only.

* Other developers: N/A (not needed for this Change)
* Release engineering: [https://pagure.io/releng/issue/10544 #10544]
* Policies and guidelines: N/A (not needed for this Change)
* Trademark approval: N/A (not needed for this Change)
* Alignment with Objectives: N/A


== Upgrade/compatibility impact ==

No impact. Files will be moved automatically during update and
everything will keep working as prior.

== How To Test ==

1. Authselect keeps working as expected after the upgrade

== User Experience ==

This change is only under the hood, it does not affect user experience.

== Dependencies ==

No dependencies.

== Contingency Plan ==
* Contingency mechanism: N/A (not a System Wide Change)
* Contingency deadline: N/A (not a System Wide Change)
* Blocks release? N/A (not a System Wide Change)

== Documentation ==
N/A (not a System Wide Change)

== Release Notes ==

Authselect state files moved from /var/lib/authselect to /etc/authselect/.state.


-- 
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

F36 Change: Authselect: Move State Files to /etc (Self-Contained Change proposal)

[Ben Cotton]

https://fedoraproject.org/wiki/Changes/Authselect_Move_State_Files_To_Etc


== Summary ==

Authselect will move several files that are currently stored at
/var/lib/authselect to /etc/authselect/.state. This does not affect
configuration backup, that will be kept at
/var/lib/authselect/backups.

The files that will be moved are:
* /var/lib/authselect/dconf-db -> /etc/authselect/.state/dconf-db
* /var/lib/authselect/dconf-locks /etc/authselect/.state/dconf-locks
* /var/lib/authselect/fingerprint-auth /etc/authselect/.state/fingerprint-auth
* /var/lib/authselect/nsswitch.conf /etc/authselect/.state/nsswitch.conf
* /var/lib/authselect/password-auth /etc/authselect/.state/password-auth
* /var/lib/authselect/postlogin /etc/authselect/.state/postlogin
* /var/lib/authselect/smartcard-auth /etc/authselect/.state/smartcard-auth
* /var/lib/authselect/system-auth /etc/authselect/.state/system-auth

== Owner ==
* Name: [[User:pbrezina| Pavel Březina]]
* Email: pbrez...@redhat.com


== Detailed Description ==

These files are used by authselect to detect changes to the system
nsswitch and PAM configurations when the configuration is updated with
an updated profile using 'authselect apply-changes'. There are two
reasons for the move:

1. The current location conflicts with ostree model where /var is not
writable during rpm transaction and this currently blocks compose of
ostree systems. [https://bugzilla.redhat.com/show_bug.cgi?id=2034360
BZ#2034360]

2. Removing these files would reduce authselect functionality, user
would need to run 'authselect select --force' to restore it. Since
/var should contain only files that can be safely removed, /etc is a
better place for them.

== Feedback ==

This change is accepted by ostree system maintainers, see
[https://bugzilla.redhat.com/show_bug.cgi?id=2034360 BZ#2034360].


== Benefit to Fedora ==
This makes authselect more compatible with ostree model.

== Scope ==
* Proposal owners: Build authselect with
--statedir=/etc/authselect/.state and move files from
/var/lib/authselect to the new location. Spec file changes only.

* Other developers: N/A (not needed for this Change)
* Release engineering: [https://pagure.io/releng/issue/10544 #10544]
* Policies and guidelines: N/A (not needed for this Change)
* Trademark approval: N/A (not needed for this Change)
* Alignment with Objectives: N/A


== Upgrade/compatibility impact ==

No impact. Files will be moved automatically during update and
everything will keep working as prior.

== How To Test ==

1. Authselect keeps working as expected after the upgrade

== User Experience ==

This change is only under the hood, it does not affect user experience.

== Dependencies ==

No dependencies.

== Contingency Plan ==
* Contingency mechanism: N/A (not a System Wide Change)
* Contingency deadline: N/A (not a System Wide Change)
* Blocks release? N/A (not a System Wide Change)

== Documentation ==
N/A (not a System Wide Change)

== Release Notes ==

Authselect state files moved from /var/lib/authselect to /etc/authselect/.state.


-- 
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: gcc-12.0.0-0.4.fc36 in rawhide

[Jonathan Wakely]

On Tue, 18 Jan 2022 at 11:01, Jonathan Wakely  wrote:

>
>
> On Mon, 17 Jan 2022 at 14:01, Ben Beasley  wrote:
>
>> Skimming through Koschei, here are a sampling of regressions that seem
>> to be associated with GCC 12. Some of these are in packages I maintain
>> directly; others are via @neuro-sig.
>>
>> With a few exceptions, I have triaged these only to the extent of
>> confirming the problem appeared at the same time as GCC 12 and noting
>> the initial error. I mostly haven’t gotten around to filing or searching
>> for bugs, upstream or downstream.
>>
>> Explicit deletion of the
>> std::string(nullptr_t)/std::string_view(nullptr_t) constructors seems
>> like it is going to be a popular cause of FTBFS in C++ packages. Use of
>> this constructor mostly happens implicitly. I think explicit use of the
>> default constructor, e.g. std::string_view(), will usually be the
>> simplest correct substitute.
>>
>
> All such uses were undefined behaviour (and should have thrown an
> exception at runtime if the code was ever executed. Fixing those is good.
>

That change now only applies when compiling as C++23, so won't affect most
packages (once the fix makes it from upstream GCC to rawhide). It would
still be good to fix code that really does construct strings and
string_views from nullptr, otherwise it will break again in a few years
when GCC defaults to -std=gnu++23.




>
>
>> New compilation errors:
>>
>> COPASI: “error: passing 'const CDataVectorN' as 'this'
>> argument discards qualifiers [-fpermissive]”
>>
>
> What's the context? Is that being used as a comparison function in a std::
> container or something?
>
>
>>
>> grpc: initializing std::string_view/absl::string_view with nullptr –
>> fixed and PR sent upstream
>>
>> python-steps: “static assertion failed: key equality predicate must be
>> invocable with two arguments of key type” via
>> c++/12/bits/hashtable_policy.h
>>
>
> Maybe a variant of https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103923
>
>
>
>>
>> vxl: “error: conversion from 'int' to 'std::__cxx11::basic_string'
>> is ambiguous” – looks like an attempt to initialize a string by
>> std::string(nullptr), which is now explicitly deleted
>> (“basic_string(nullptr_t) = delete”)
>>
>
> If it's actually initializing it with nullptr, that's just undefined (and
> going to be ill-formed in C++23) and the code should be fixed.
>
> If it's like the nlohmann:json case, I need to investigate more whether
> it's a defect in the C++23 spec or the code should be fixed.
>

Turns out it's both. The C++23 change breaks the json lib (and they have a
fix) but I made it apply to all of C++11/14/17/20/23, which is incorrect
because it breaks code that should be valid in C++20. Fixed in GCC upstream
now.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: gcc-12.0.0-0.4.fc36 in rawhide

[Jonathan Wakely]

On Tue, 18 Jan 2022 at 11:04, Jonathan Wakely  wrote:

>
>
> On Tue, 18 Jan 2022 at 10:29, Frantisek Zatloukal 
> wrote:
>
>>
>>
>> On Fri, Jan 14, 2022 at 3:33 PM Jakub Jelinek  wrote:
>>
>>> If there are bugs on the compiler side, please let me know immediately,
>>> so that those bugs can be fixed before the mass rebuild next week.
>>>
>>
>> While I was trying to rebuild some Intel components, i've encountered
>> this issue, which seems to be caused by libstdc. It affects
>> intel-graphics-compiler (not yet in Fedora). That is compiled with clang,
>> however, since gcc/libstdc 12, I am hitting this:
>>
>> /builddir/build/BUILD/intel-graphics-compiler-igc-1.0.9933/IGC/VectorCompiler/lib/GenXCodeGen/GenXLiveness.cpp:590:46:
>> error: call to constructor of 'LiveRangeMap_t::value_type' (aka 'pair> llvm::genx::SimpleValue, llvm::genx::LiveRange *>') is ambiguous
>>   auto [i, isInserted] =
>> LiveRangeMap.insert(LiveRangeMap_t::value_type(V, 0));
>>  ^
>>  
>> /usr/bin/../lib/gcc/x86_64-redhat-linux/12/../../../../include/c++/12/bits/stl_pair.h:425:17:
>> note: candidate constructor [with _U1 = const llvm::genx::SimpleValue, _U2
>> = llvm::genx::LiveRange *, $2 = true]
>>   constexpr pair(const _T1& __a, const _T2& __b)
>> ^
>> /usr/bin/../lib/gcc/x86_64-redhat-linux/12/../../../../include/c++/12/bits/stl_pair.h:492:18:
>> note: candidate constructor [with _U1 = llvm::genx::SimpleValue &, $1 =
>> true]
>>constexpr pair(_U1&& __x, __null_ptr_constant)
>>  ^
>> 1 error generated.
>>
>> I've tried to locally recompile clang and llvm against the new libstdc
>> (as it seems ambiguousness is caused by #if _GLIBCXX_USE_DEPRECATED being
>> met), but that didn't help. Maybe I am missing some library that needs to
>> be recompiled too. Anyhow, is this expected behavior?
>>
>> The affected file is this one:
>> https://github.com/intel/intel-graphics-compiler/blob/master/IGC/VectorCompiler/lib/GenXCodeGen/GenXLiveness.cpp
>>
>
>
> I think the code is just wrong, and should use nullptr instead of 0 in
> that initializer on line 590.
>
> It's related to https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101124
> though. I tried to keep that old incorrect code working, but apparently
> failed.
>

It was a GCC regression in my std::pair changes, fixed now.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Schedule for Tuesday's FESCo Meeting (2022-01-18)

[Miro Hrončok]

Following is the list of topics that will be discussed in the
FESCo meeting Tuesday at 18:00UTC in #fedora-meeting on
irc.libera.chat.

To convert UTC to your local time, take a look at
  http://fedoraproject.org/wiki/UTCHowto

or run:
  date -d '2022-01-18 18:00 UTC'


Links to all issues to be discussed can be found at:
https://pagure.io/fesco/report/meeting_agenda

= Discussed and Voted in the Ticket =

F36 Change: LLVM 14
https://pagure.io/fesco/issue/2726
APPROVED (+7,0,-0)

F36 Change: Ruby 3.1
https://pagure.io/fesco/issue/2727
APPROVED (+8,0,-0)

F36 Change: %set_build_flags for %build, %check, and %install phases
https://pagure.io/fesco/issue/2728
APPROVED (+7,0,-0)

F36 Change: Default To Noto Fonts
https://pagure.io/fesco/issue/2729
APPROVED (+5,0,-0)

F36 Change: Hunspell Dictionary dir change
https://pagure.io/fesco/issue/2730
APPROVED (+4,0,-0)

Nonresponsive maintainer: Mike xenithorb
https://pagure.io/fesco/issue/2696
APPROVED (+2,0,-0)

Nonresponsive maintainer: Dhiru Kholia halfie
https://pagure.io/fesco/issue/2718
self APPROVED by halfie

Nonresponsive maintainer: Rüdiger Landmann rlandmann
https://pagure.io/fesco/issue/2723
APPROVED (+3,0,-0)

Unresponsive Maintainer process - hubbitus (Pavel Alexeev)
https://pagure.io/fesco/issue/2724
APPROVED 4 years ago (+6, 0, -0)
APPROVED to orphan all packages etc. (+3,0,0)


= Followups =

#2711 F36 Change: Enable fs-verity in RPM
https://pagure.io/fesco/issue/2711

#2721 F36 Change: DIGLIM
https://pagure.io/fesco/issue/2721

#2731 F36 Change: Relocate RPM database to /usr
https://pagure.io/fesco/issue/2731


= Open Floor =

For more complete details, please visit each individual
issue.  The report of the agenda items can be found at
https://pagure.io/fesco/report/meeting_agenda

If you would like to add something to this agenda, you can
reply to this e-mail, file a new issue at
https://pagure.io/fesco, e-mail me directly, or bring it
up at the end of the meeting, during the open floor topic. Note
that added topics may be deferred until the following meeting.

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: gcc-12.0.0-0.4.fc36 in rawhide

[Jakub Jelinek]

On Tue, Jan 18, 2022 at 05:40:31PM +0100, Adrian Reber wrote:
> > If there are bugs on the compiler side, please let me know immediately,
> > so that those bugs can be fixed before the mass rebuild next week.
> 
> Not sure if it is a bug, CRIU no longer works with GCC 12.
> 
> CRIU creates something called 'parasite code' which is injected into
> running processes for checkpointing and that part is built with
> '-nostdlib'. Starting with GCC 12 we see 'strlen()' being pulled into
> the parasite code which it wasn't with GCC 11.

strlen is a standard C function, so I don't see any bug in that being used
unless you do a freestanding compilation (-nostdlib isn't that).
If you mail me preprocessed source of handle-elf-host.c + gcc
command line used to compile it, I can have a look what exactly changed.

> https://kojipkgs.fedoraproject.org/work/tasks/6033/81406033/build.log
> 
> gcc -c -O2 -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 -m64 -mtune=generic 
> -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -O2 -g 
> -Wall -Wformat-security -Wdeclaration-after-statement -Wstrict-prototypes 
> -DCONFIG_X86_64 -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -DCONFIG_HAS_LIBBSD 
> -DCONFIG_HAS_SELINUX -DCONFIG_GNUTLS -DCONFIG_HAS_NFTABLES_LIB_API_1 
> -DCONFIG_COMPAT -iquote include/ -DCONFIG_HAS_LIBBSD -DCONFIG_HAS_SELINUX 
> -DCONFIG_GNUTLS -DCONFIG_HAS_NFTABLES_LIB_API_1 -DCONFIG_COMPAT -I 
> ./compel/include/uapi -fno-strict-aliasing -iquote criu/include -iquote 
> include -iquote images -iquote criu/arch/x86/include -iquote . 
> -I/usr/include/libnl3 -DSYSCONFDIR='"/etc"' 
> -DGLOBAL_CONFIG_DIR='"/etc/criu/"' -DDEFAULT_CONFIG_FILENAME='"default.conf"' 
> -DUSER_CONFIG_DIR='".criu/"' -DCR_NOGLIBC -Wstrict-prototypes 
> -fno-stack-protector -nostdlib -fomit-frame-pointer -fpie -I 
> ./compel/include/uapi -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=0 
> -Wp,-U_FORTIFY_SOURCE -Wp,-D_FORTIFY_SOURCE=0 criu/pie/restorer.c -o 
> criu/pie/restorer.o
> ld  -r -z noexecstack -T ./compel/arch/x86/scripts/compel-pack.lds.S  -o 
> criu/pie/restorer.built-in.o  criu/pie/parasite-vdso.o 
> ./criu/arch/x86/vdso-pie.o ./criu/arch/x86/restorer.o 
> ./criu/arch/x86/restorer_unmap.o ./criu/arch/x86/sigaction_compat_pie.o 
> criu/pie/restorer.o criu/pie/pie.lib.a ./compel/plugins/std.lib.a
> ./compel/compel-host hgen -f criu/pie/restorer.built-in.o -o 
> criu/pie/restorer-blob.h
> Error (compel/src/lib/handle-elf-host.c:337): Unexpected undefined symbol: 
> `strlen'. External symbol in PIE?
> make[2]: *** [criu/pie/Makefile:58: criu/pie/restorer-blob.h] Error 255
> make[1]: *** [criu/Makefile:59: pie] Error 2
> make: *** [Makefile:250: criu] Error 2
> 
> Not sure why there is 'strlen()' pulled in with GCC 12. Any ideas?

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

[Bug 2041248] perl-XML-Stream for EPEL 9

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



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


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2041248
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Rawhide kernel crash

[Justin Forbes]

On Tue, Jan 18, 2022 at 6:30 AM Leigh Scott  wrote:
>
> > On Mon, Nov 8, 2021 at 6:56 AM edmond pilon  >
> > These configs are in preparation for an F36 potential feature, and
> > were not intended to work flawlessly on F35 or earlier. They were
> > backed out from the fedora-5.15 branch as soon as it was created
> > because that branch targets stable Fedora.   While simpledrm will work
> > for many systems at this time, it seems to have issues with nvidia
> > drivers at least.
> >
> > Justin
>
>
> The latest f35 kernel build has enabled simpledrm
>
> $ grep _SIMPLE /boot/config-5.16.1-200.fc35.x86_64
> CONFIG_SYSFB_SIMPLEFB=y
> CONFIG_MEDIA_TUNER_SIMPLE=m
> CONFIG_DRM_SIMPLEDRM=y
> CONFIG_SND_SOC_SIMPLE_AMPLIFIER=m
> CONFIG_SND_SOC_SIMPLE_MUX=m
> CONFIG_SND_SIMPLE_CARD_UTILS=m
> CONFIG_SND_SIMPLE_CARD=m
> CONFIG_USB_SERIAL_SIMPLE=m
> # CONFIG_IIO_SIMPLE_DUMMY is not set

Indeed it does, though kernel build is not kernel update.  It will be
a good 2 weeks before 5.16 kernels are offered as an official update.
The point is to get more testing on simpledrm, so I plan to keep it on
at least through the first test week kernels to get some feedback on
it.

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

Re: gcc-12.0.0-0.4.fc36 in rawhide

[Adrian Reber]

On Fri, Jan 14, 2022 at 03:31:43PM +0100, Jakub Jelinek wrote:
> gcc 12 snapshot has landed as the system compiler into rawhide today.
> GCC 12 is going to enter its stage4 development phase (only regression
> and documentation bugfixes allowed) on Monday 17th, so there should be
> just those bugfixes and not new features etc. anymore.
> https://gcc.gnu.org/gcc-12/changes.html lists important changes,
> most important is probably that vectorization is enabled at -O2 now
> which is the option with most of the distribution is built with.
> 
> https://gcc.gnu.org/gcc-12/porting_to.html is so far incomplete and lists
> some cases where people need to adjust their code.  Other things
> include the usual C++ header changes, where previously some standard
> header included some other header as an implementation detail but it doesn't
> any longer and so code that relied on such indirect include that isn't
> required by the standard needs to include the header that provides whatever
> it relies on.  Or e.g. packages using -Werror where new warnings are
> reported with the newer compiler and -Werror results in build failures.
> 
> If there are bugs on the compiler side, please let me know immediately,
> so that those bugs can be fixed before the mass rebuild next week.

Not sure if it is a bug, CRIU no longer works with GCC 12.

CRIU creates something called 'parasite code' which is injected into
running processes for checkpointing and that part is built with
'-nostdlib'. Starting with GCC 12 we see 'strlen()' being pulled into
the parasite code which it wasn't with GCC 11.

https://kojipkgs.fedoraproject.org/work/tasks/6033/81406033/build.log

gcc -c -O2 -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 -m64 -mtune=generic 
-fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -O2 -g 
-Wall -Wformat-security -Wdeclaration-after-statement -Wstrict-prototypes 
-DCONFIG_X86_64 -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -DCONFIG_HAS_LIBBSD 
-DCONFIG_HAS_SELINUX -DCONFIG_GNUTLS -DCONFIG_HAS_NFTABLES_LIB_API_1 
-DCONFIG_COMPAT -iquote include/ -DCONFIG_HAS_LIBBSD -DCONFIG_HAS_SELINUX 
-DCONFIG_GNUTLS -DCONFIG_HAS_NFTABLES_LIB_API_1 -DCONFIG_COMPAT -I 
./compel/include/uapi -fno-strict-aliasing -iquote criu/include -iquote include 
-iquote images -iquote criu/arch/x86/include -iquote . -I/usr/include/libnl3 
-DSYSCONFDIR='"/etc"' -DGLOBAL_CONFIG_DIR='"/etc/criu/"' 
-DDEFAULT_CONFIG_FILENAME='"default.conf"' -DUSER_CONFIG_DIR='".criu/"' 
-DCR_NOGLIBC -Wstrict-prototypes -fno-stack-protector -nostdlib 
-fomit-frame-pointer -fpie -I ./compel/include/uapi -U_FORTIFY_SOURCE 
-D_FORTIFY_SOURCE=0 -Wp,-U_FORTIFY_SOURCE -Wp,-D_FORTIFY_SOURCE=0 
criu/pie/restorer.c -o criu/pie/restorer.o
ld  -r -z noexecstack -T ./compel/arch/x86/scripts/compel-pack.lds.S  -o 
criu/pie/restorer.built-in.o  criu/pie/parasite-vdso.o 
./criu/arch/x86/vdso-pie.o ./criu/arch/x86/restorer.o 
./criu/arch/x86/restorer_unmap.o ./criu/arch/x86/sigaction_compat_pie.o 
criu/pie/restorer.o criu/pie/pie.lib.a ./compel/plugins/std.lib.a
./compel/compel-host hgen -f criu/pie/restorer.built-in.o -o 
criu/pie/restorer-blob.h
Error (compel/src/lib/handle-elf-host.c:337): Unexpected undefined symbol: 
`strlen'. External symbol in PIE?
make[2]: *** [criu/pie/Makefile:58: criu/pie/restorer-blob.h] Error 255
make[1]: *** [criu/Makefile:59: pie] Error 2
make: *** [Makefile:250: criu] Error 2

Not sure why there is 'strlen()' pulled in with GCC 12. Any ideas?

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

Re: Self Introduction: Dorinda Bassey

[Tim Orling]

On Tue, Jan 18, 2022 at 4:49 AM Felipe Borges  wrote:

> On Tue, Jan 18, 2022 at 1:21 PM Dorinda Bassey  wrote:
> >
> > Hi Everyone,
> >
> > My name is Dorinda and I am an Associate software Engineer at Red Hat,
> > I'm passionate about software development, contributing to the growth of
> communities and I have
> > some experience contributing to FOSS projects.
> > I am interested in becoming a package maintainer.
> > I learnt how to create RPM packages and build with mock and copr,
> > My plan so far is to maintain gpuvis and gpu-trace packages(yet to
> submit).
> > I'm also open to maintaining some more in the future.
>
> Welcome to the Fedora Project!
>

Nice to see a “new” familiar face. Welcome, Dorinda.

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

[Bug 2036510] Please branch and build perl-Config-General for EPEL-9

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



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


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2036510
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

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

[Fedora compose checker]

No missing expected images.

Compose FAILS proposed Rawhide gating check!
19 of 43 required tests failed, 13 results missing
openQA tests matching unsatisfied gating requirements shown with **GATING** 
below

Failed openQA tests: 93/228 (x86_64), 61/159 (aarch64)

New failures (same test not failed in Fedora-Rawhide-20220117.n.1):

ID: 1107604 Test: x86_64 Server-boot-iso install_default@uefi **GATING**
URL: https://openqa.fedoraproject.org/tests/1107604
ID: 1107605 Test: x86_64 Server-boot-iso install_default **GATING**
URL: https://openqa.fedoraproject.org/tests/1107605
ID: 1107607 Test: x86_64 Server-dvd-iso 
install_blivet_standard_partition_ext4
URL: https://openqa.fedoraproject.org/tests/1107607
ID: 1107608 Test: x86_64 Server-dvd-iso 
install_blivet_standard_partition_ext4@uefi
URL: https://openqa.fedoraproject.org/tests/1107608
ID: 1107609 Test: x86_64 Server-dvd-iso 
install_blivet_btrfs_preserve_home_uefi@uefi
URL: https://openqa.fedoraproject.org/tests/1107609
ID: 1107610 Test: x86_64 Server-dvd-iso install_btrfs_preserve_home
URL: https://openqa.fedoraproject.org/tests/1107610
ID: 1107611 Test: x86_64 Server-dvd-iso install_lvm_ext4@uefi
URL: https://openqa.fedoraproject.org/tests/1107611
ID: 1107612 Test: x86_64 Server-dvd-iso install_standard_partition_ext4@uefi
URL: https://openqa.fedoraproject.org/tests/1107612
ID: 1107613 Test: x86_64 Server-dvd-iso install_default@uefi **GATING**
URL: https://openqa.fedoraproject.org/tests/1107613
ID: 1107614 Test: x86_64 Server-dvd-iso install_default_upload **GATING**
URL: https://openqa.fedoraproject.org/tests/1107614
ID: 1107616 Test: x86_64 Server-dvd-iso install_blivet_btrfs_preserve_home
URL: https://openqa.fedoraproject.org/tests/1107616
ID: 1107617 Test: x86_64 Server-dvd-iso install_repository_hd_variation
URL: https://openqa.fedoraproject.org/tests/1107617
ID: 1107619 Test: x86_64 Server-dvd-iso install_lvm_ext4
URL: https://openqa.fedoraproject.org/tests/1107619
ID: 1107623 Test: x86_64 Server-dvd-iso install_vncconnect_client
URL: https://openqa.fedoraproject.org/tests/1107623
ID: 1107626 Test: x86_64 Server-dvd-iso 
install_btrfs_preserve_home_uefi@uefi
URL: https://openqa.fedoraproject.org/tests/1107626
ID: 1107629 Test: x86_64 Server-dvd-iso install_vnc_server
URL: https://openqa.fedoraproject.org/tests/1107629
ID: 1107631 Test: x86_64 Server-dvd-iso install_standard_partition_ext4
URL: https://openqa.fedoraproject.org/tests/1107631
ID: 1107636 Test: x86_64 Server-dvd-iso install_blivet_lvm_ext4
URL: https://openqa.fedoraproject.org/tests/1107636
ID: 1107637 Test: x86_64 Server-dvd-iso install_blivet_lvm_ext4@uefi
URL: https://openqa.fedoraproject.org/tests/1107637
ID: 1107647 Test: x86_64 Server-dvd-iso install_vncconnect_server
URL: https://openqa.fedoraproject.org/tests/1107647
ID: 1107649 Test: x86_64 Server-dvd-iso install_vnc_client
URL: https://openqa.fedoraproject.org/tests/1107649
ID: 1107660 Test: x86_64 Everything-boot-iso install_default **GATING**
URL: https://openqa.fedoraproject.org/tests/1107660
ID: 1107661 Test: x86_64 Everything-boot-iso install_default@uefi **GATING**
URL: https://openqa.fedoraproject.org/tests/1107661
ID: 1107662 Test: x86_64 Everything-boot-iso memory_check
URL: https://openqa.fedoraproject.org/tests/1107662
ID: 1107663 Test: x86_64 Everything-boot-iso memory_check@uefi
URL: https://openqa.fedoraproject.org/tests/1107663
ID: 1107690 Test: x86_64 KDE-live-iso install_default_upload **GATING**
URL: https://openqa.fedoraproject.org/tests/1107690
ID: 1107691 Test: x86_64 KDE-live-iso install_no_user **GATING**
URL: https://openqa.fedoraproject.org/tests/1107691
ID: 1107696 Test: x86_64 KDE-live-iso install_default@uefi **GATING**
URL: https://openqa.fedoraproject.org/tests/1107696
ID: 1107746 Test: aarch64 Server-dvd-iso install_blivet_lvm_ext4@uefi
URL: https://openqa.fedoraproject.org/tests/1107746
ID: 1107748 Test: aarch64 Server-dvd-iso install_vnc_server@uefi
URL: https://openqa.fedoraproject.org/tests/1107748
ID: 1107751 Test: aarch64 Server-dvd-iso install_default_upload@uefi
URL: https://openqa.fedoraproject.org/tests/1107751
ID: 1107752 Test: aarch64 Server-dvd-iso 
install_blivet_btrfs_preserve_home_uefi@uefi
URL: https://openqa.fedoraproject.org/tests/1107752
ID: 1107760 Test: aarch64 Server-dvd-iso 
install_btrfs_preserve_home_uefi@uefi
URL: https://openqa.fedoraproject.org/tests/1107760
ID: 1107761 Test: aarch64 Server-dvd-iso 
install_standard_partition_ext4@uefi
URL: https://openqa.fedoraproject.org/tests/1107761
ID: 1107762 Test: aarch64 Server-dvd-iso install_vnc_client@uefi
URL: https://openqa.fedoraproject.org/tests/1107762
ID: 1107763 Test: aarch64 Server-dvd-iso install_vncconnect_client@uefi
URL: https://openqa.fedoraproject.org/tests/1107763
ID: 1107774 Test: aarch64 Server-dvd-iso 
install_repository_hd_variation@uefi
URL: 

[EPEL-devel] [Fedocal] Reminder meeting : EPEL Steering Committee

[tdawson]

Dear all,

You are kindly invited to the meeting:
   EPEL Steering Committee on 2022-01-19 from 16:00:00 to 17:00:00 US/Eastern
   At fedora-meet...@irc.libera.chat

The meeting will be about:
This is the weekly EPEL Steering Committee Meeting.

A general agenda is the following:

#meetingname EPEL
#topic Intros
#topic Old Business
#topic EPEL-7
#topic EPEL-8
#topic EPEL-9
#topic Openfloor
#endmeeting




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

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

[Bug 2041279] Please branch and build perl-Convert-TNEF epel9

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



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


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2041279
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2041284] Please branch and build perl-Test-Manifest in epel9

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



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


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2041284
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2041174] Please branch and build perl-Crypt-PasswdMD5 in epel9

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



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


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2041174
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: gcc-12.0.0-0.4.fc36 in rawhide

[Sérgio Basto]

On Mon, 2022-01-17 at 14:36 +, Sérgio Basto wrote:
> On Mon, 2022-01-17 at 15:10 +0100, Vitaly Zaitsev via devel wrote:
> > On 17/01/2022 15:00, Ben Beasley wrote:
> > > dependency “json”: https://github.com/nlohmann/json/issues/3138
> > 
> > https://bugzilla.redhat.com/show_bug.cgi?id=2041187
> > 
> 
> Rawhide compose doomed again [1] :( , I still haven't the results of 
> koschei opencv altivec build with gcc-12.0.0-0.5, it failed with gcc-
> 12.0.0-0.4 [2] 
> 


Build with gcc-12.0.0-0.5 not fixed the error related with altivec 

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



> 
> [2]
> https://koschei.fedoraproject.org/package/opencv?collection=f36
> 
> [1]
> https://kojipkgs.fedoraproject.org/compose/rawhide/
> 
> 
> -- 
> Sérgio M. B.
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure

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

Re: gcc-12.0.0-0.4.fc36 in rawhide

[Frantisek Zatloukal]

On Tue, Jan 18, 2022 at 12:25 PM Jonathan Wakely  wrote:

> PR sent:
> https://github.com/intel/intel-graphics-compiler/pull/226
>

Thanks! Added a comment to that, works flawlessly!


-- 

Best regards / S pozdravem,

František Zatloukal
Quality Engineer
Red Hat
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Request assistance getting a package (usbrelay) into Fedora

[Mark E. Fuller]

Hi Darryl,

My emails keep bouncing when I try to write to you directly.

I'll try to block off some time in the coming week to take a stab at 
drafting a package for usbrelay and then get back to you.


Looking forward to working with you.
In the meantime, please send me a message directly so we can move off 
the list.


Best,
fuller

Mark E. Fuller, Ph.D.
ful...@fedoraproject.org
ful...@stossrohr.net
@fuller:one.ems.host
https://www.stossrohr.net
PGP Fingerprint: 73F1 A30C BDF4 DB4B C75F FD0F D599 E76C FFCA BF60

On 18/01/2022 5:04, Darryl Bond wrote:

Mark,
  Petr's suggestion I find a co maintainer sounds very sensible. It's unlikely 
I'll need to do any other package. I would be pleased to assist you if you 
chose to be that person.

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


OpenPGP_0xD599E76CFFCABF60.asc
Description: OpenPGP public key


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

Re: IMA signing questions

[Ken Dreyer]

On Mon, Jan 17, 2022 at 4:44 PM Ken Dreyer  wrote:
> Something else I'm wondering: rpmsign writes those four-byte "keyid"
> values to my FILESIGNATURE entries even if I don't have a public cert
> at all. How does it do that? I see verify_rpm.py checks the RPM's
> keyid values against the final four bytes of a sha1 of a public
> certificate, but what if I haven't generated that yet?

I understand this part about public and private certs now.
python-cryptography can read the values from the RSA private keyfile
to determine the public key values.

This Python script will find the IMA-style keyid from a RSA private keyfile:

with open('privatekey.pem', 'rb') as f:
key = serialization.load_pem_private_key(f.read(),
 password=None,
 backend=default_backend())

public_key = key.public_key()

# The "keyid" is the SHA1 hash of the DER-encoded ASN.1 sequence of the
# modulus and exponent of an RSA public key. (public_key.public_numbers() "n"
# and "e"). This method does it for us:
public_key_id = x509.SubjectKeyIdentifier.from_public_key(public_key)

# The IMA signature's "keyid" is the last four bytes of this SHA1 digest.
ima_keyid = public_key_id.digest[-4:]
print(ima_keyid)


I've been concerned for a while that Koji uses small GPG key ID
values, for the reasons explained at https://evil32.com/

When it comes to IMA signature handling with Koji, I don't want to use
small key ID lengths for that either. Even sha1 is pretty weak now. Is
there any chance of using stronger key IDs for IMA?

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

[Bug 2038180] Add perl-XML-CommonNS to EPEL 9

[bugzilla]

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



--- Comment #1 from Petr Pisar  ---
https://pagure.io/releng/fedora-scm-requests/issue/41088


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

RE: F36 Change: DIGLIM (System-Wide Change proposal)

[Roberto Sassu via devel]

Hi everyone

I recently sent to the kernel mailing lists a patch set to support
PGP keys and signatures.

Other than allowing the appraisal of RPM headers without
changes to the building infrastructure, it would also simplify
key management for the use cases requiring file or fsverity
signatures (no need for a secondary key).

This is the link of the patch set:

https://lore.kernel.org/linux-integrity/2022080318.591029-1-roberto.sa...@huawei.com/

One point of the discussion was if there is the need to support
PGP in the kernel, or if a distribution should adapt its key
management to be compatible with key types currently available
in the kernel.

It would be great if you could comment on this patch set, from
the perspective of people managing a Linux distribution. Also,
any thought related to the patch set would be appreciated.

Thanks

Roberto

HUAWEI TECHNOLOGIES Duesseldorf GmbH, HRB 56063
Managing Director: Li Peng, Zhong Ronghua
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

F36 Change: Wayland by Default for SDDM (Self-Contained Change proposal)

[Ben Cotton]

https://fedoraproject.org/wiki/Changes/WaylandByDefaultForSDDM

= Wayland by Default for SDDM =

== Summary ==
Change the default display server mode for SDDM to use a Wayland-based
greeter rather than an X11-based one.

== Owner ==
* Name: [[User:Ngompa|Neal Gompa]], [[User:Rdieter|Rex Dieter]],
[[User:Jgrulich|Jan Grulich]]
* Email: ngomp...@gmail.com, rdie...@gmail.com, jgrul...@redhat.com
* Product: KDE Spin, Kinoite
* Responsible WG: KDE SIG


== Detailed Description ==
With [https://github.com/sddm/sddm/pull/1393 the work done upstream in
SDDM to support using a Wayland based greeter] and
[[Changes/ReplaceFbdevDrivers|the introduction of SimpleDRM to fix the
broken fallback when platform drivers are unavailable]], it is now
possible for the Fedora KDE variants (the regular spin and Kinoite) to
move to Wayland for the login manager, which effectively completes the
switch to Wayland for these variants.


== Benefit to Fedora ==
As originally detailed in [[Changes/WaylandByDefaultForPlasma|the
Change to switch Plasma to Wayland by default]], Fedora is a leader in
advancing the adoption of the Wayland protocol as part of the overall
strategy to improve the Linux graphical software stack. We have been
successful in helping drive Wayland forward in the Plasma Desktop, and
we intend to do the same for SDDM.

== Scope ==
* Proposal owners:
** Upgrade {{package|sddm}} to the latest snapshot and introduce
mutually exclusive sddm-wayland-generic and
sddm-x11 greeter configuration packages.
** Modify {{package|plasma-workspace}} to switch SDDM to Wayland
*** Enable installation of the SDDM Wayland configuration snippet and
ship as sddm-wayland-plasma that is mutually exclusive
with the other sddm greeter configuration packages. This package will
supplement {{package|sddm}} and plasma-workspace-wayland
to be automatically installed together.
** Modify @kde-desktop comps group for Fedora Linux 36 to
include sddm-wayland-plasma for the media.


* Other developers: N/A (not needed for this Change)

* Release engineering: [https://pagure.io/releng/issue/10536 #10536]
* Policies and guidelines: N/A (not needed for this Change)
* Trademark approval: N/A (not needed for this Change)
* Alignment with Objectives: N/A


== Upgrade/compatibility impact ==
On upgrade to Fedora Linux 36, SDDM will be transparently switched
from the X11 greeter to the Wayland one leveraging kwin. In order to
override this, the user can do one of the following:
* Drop in a configuration file in /etc/sddm.conf.d to set
the display server back to X11
* Swap back to X11 with the configuration package: dnf swap
sddm-wayland-plasma sddm-x11


== How To Test ==
Once the SDDM and Plasma Wayland changes are made, Rawhide users can
try this by using nightly KDE ISOs and using them normally to install
and run a Rawhide KDE Plasma environment.

== User Experience ==
Ideally, there should be no noticeable impact on the user experience,
though users may notice that things operate more smoothly and with
slightly lower resources.

== Dependencies ==
This change is dependent on [[Changes/ReplaceFbdevDrivers|the Change
to replace fbdev with SimpleDRM]]. Without that Change, we will need
to keep SDDM using X11 because otherwise the fallbacks are broken when
drivers do not work.

== Contingency Plan ==
* Contingency mechanism: Update comps and {{package|plasma-workspace}}
so that sddm-x11 is shipped instead.
* Contingency deadline: beta freeze
* Blocks release? Yes


== Documentation ==
N/A (not a System Wide Change)

== Release Notes ==
SDDM, the login manager for the Fedora variants using the KDE Plasma
Desktop, now uses the Wayland display system.


-- 
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

F36 Change: Ruby on Rails 7.0 (Self-Contained Change proposal)

[Ben Cotton]

https://fedoraproject.org/wiki/Changes/Ruby_on_Rails_7.0

== Summary ==
Ruby on Rails 7.0 is the latest version of well known web framework
written in Ruby.

== Owner ==
* Name: [[User:pvalena| Pavel Valena]], [[User:jprokop| Jarek Prokop]]
* Email: pval...@redhat.com, jpro...@redhat.com,
ruby-...@lists.fedoraproject.org


== Detailed Description ==
The Ruby on Rails stack is evolving quickly and Fedora needs to keep
pace with it. Therefore the whole Ruby on Rails stack should be
updated from 6.1 in Fedora 35 to 7.0 (latest version) in Fedora 36.
This will ensure that all the Ruby developers using Fedora have the
latest and greatest RPM-packaged Ruby on Rails.

== Benefit to Fedora ==
This update will keep Fedora up-to-date and will ensure that the
current Ruby on Rails developers stay with us as they will get support
for system-packaged Ruby on Rails of the latest version. Update to
Rails 7.0 contains hundreds of fixes and improvements across all the
frameworks. For new features, please see [#User_Experience User
Experience].

== Scope ==
* Proposal owners:
** The whole Rails stack has to be updated.
** Some dependencies of the Rails stack will need update.

=== Packages need to be created/updated ===

* Rails bug: [https://bugzilla.redhat.com/show_bug.cgi?id=2032639 #2032639]
** Specific changes: (see wiki)

* Current development state can be observed in
[https://copr.fedorainfracloud.org/coprs/pvalena/ruby-on-rails/
pvalena/ruby-on-rails] COPR repository.
** Current status: '''version 7.0.0''' built and tested

* Other developers: Update Rails dependent packages to be working with
Ruby on Rails 7.0
* Policies and guidelines: N/A (not a System Wide Change)
* Trademark approval: N/A (not needed for this Change)

== Upgrade/compatibility impact ==
Web applications build above Ruby on Rails framework might need to be
updated. Official upstream upgrade guide might come handy:
http://guides.rubyonrails.org/upgrading_ruby_on_rails.html

== How To Test ==
* No special hardware is needed.
* Some additional adjustments to dependencies are needed to start the
default app. Example:
** https://github.com/pvalena/theprototype/blob/main/rails/test.sh


=== To test only Rails itself ===

dnf install rubygem-rails
rails new app
cd app && rails s

* Go to http://127.0.0.1:3000/ and make sure you are running Rails 7.0.x

=== To test the complete feature including generating a new Rails app
using RPM ===

dnf group install 'Ruby on Rails'
rails new app --skip-bundle && cd app
rails s

* Go to http://127.0.0.1:3000/ and make sure you are running Rails 7.0.x

== User Experience ==
* New version of Ruby on Rails (7.0) available
* The most significant Rails 7.0 features:
** No-Node default approach to the front end
** Hotwire’s combination of Turbo and Stimulus
** Easily use any JavaScript bundler
** Encrypted attributes in Active Record
** Asynchronous Query Loading
** Zeitwerk autoloader is used exclusively

== Dependencies ==
* There are several packages, which depends on Ruby on Rails framework.
* These needs to be surely updated:
** (none)
* Following gems don't support Rails 7.0 right now and would be broken
by the update:
** (none)
* As Rails requires Ruby >= 2.7, the platform less than the version
can not use Rails 7.0.

== Contingency Plan ==
* Contingency mechanism: None needed. Rails stack won't be updated
until all its dependencies are in Rawhide. After that, it will be a
simple matter of updating the core packages (and their dependencies)
via side-tag.
* Contingency deadline: N/A (not a System Wide Change)
* Blocks release? No
* Blocks product? No

== Documentation ==
* http://api.rubyonrails.org/

== Release Notes ==
* https://rubyonrails.org/2021/12/15/Rails-7-fulfilling-a-vision
* https://edgeguides.rubyonrails.org/7_0_release_notes.html


-- 
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

F36 Change: MLT-7 (Self-Contained Change proposal)

[Ben Cotton]

https://fedoraproject.org/wiki/Changes/F36MLT-7

== Summary ==
update MLT to version 7.4 (latest version)

== Owner ==
* Name: [[User:sergiomb| Sérgio Basto]]
* Email: sergi...@fedoraproject.org


== Detailed Description ==
Update of MLT from v6 to v7 breaks the builds, binaries changed the
name and devel files changed the location [1], authors argue that
facilitates have 2 versions of MLT at same time, but I personally
don't want keep to versions of MLT because MLT just 3 or 5 projects
that use it,

[1]
https://github.com/mltframework/mlt/issues/713


== Benefit to Fedora ==
Up-to-date and latest MLT release will be delivered to Fedora users.


== Scope ==
* Proposal owners: [[User:Sergiomb | Sérgio Basto]]
[[https://accounts.fedoraproject.org/user/martinkg/ | Martin
Gansser]]

* Other developers: [[User:Kwizart | Nicolas Chauvet]]
* Release engineering:
* Policies and guidelines: N/A (not needed for this Change)
* Trademark approval: N/A (not needed for this Change)
* Alignment with Objectives:


== Upgrade/compatibility impact ==
We need update ETL , synfig  and synfigstudio  from version 1.40 to
version 1.5.1 .

webvfx (THE PROJECT IS DEPRECATED BY THE MLT TEAM AND NO LONGER
MAINTAINED) we may retire it or build it without MLT support.

== How To Test ==
Run the new synfigstudio and work with it, testing the tasks that user
already did with the previous version

== User Experience ==
They will have updated tools

== Dependencies ==
Already explained on Upgrade/compatibility impact

== Contingency Plan ==

* Contingency mechanism: (What to do?  Who will do it?) (not a System
Wide Change) report upstream and apply fixes ASAP
* Contingency deadline: N/A (not a System Wide Change)
* Blocks release? No

== Documentation ==
https://www.mltframework.org/docs/

== Release Notes ==
post https://www.mltframework.org/blog/v7.0.0_released/

and blog it self https://www.mltframework.org/blog/


-- 
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Fedocal] Reminder meeting : Fedora Source-git SIG

[csomh]

Dear all,

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

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

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

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


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

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

F36 Change: Ruby on Rails 7.0 (Self-Contained Change proposal)

[Ben Cotton]

https://fedoraproject.org/wiki/Changes/Ruby_on_Rails_7.0

== Summary ==
Ruby on Rails 7.0 is the latest version of well known web framework
written in Ruby.

== Owner ==
* Name: [[User:pvalena| Pavel Valena]], [[User:jprokop| Jarek Prokop]]
* Email: pval...@redhat.com, jpro...@redhat.com,
ruby-...@lists.fedoraproject.org


== Detailed Description ==
The Ruby on Rails stack is evolving quickly and Fedora needs to keep
pace with it. Therefore the whole Ruby on Rails stack should be
updated from 6.1 in Fedora 35 to 7.0 (latest version) in Fedora 36.
This will ensure that all the Ruby developers using Fedora have the
latest and greatest RPM-packaged Ruby on Rails.

== Benefit to Fedora ==
This update will keep Fedora up-to-date and will ensure that the
current Ruby on Rails developers stay with us as they will get support
for system-packaged Ruby on Rails of the latest version. Update to
Rails 7.0 contains hundreds of fixes and improvements across all the
frameworks. For new features, please see [#User_Experience User
Experience].

== Scope ==
* Proposal owners:
** The whole Rails stack has to be updated.
** Some dependencies of the Rails stack will need update.

=== Packages need to be created/updated ===

* Rails bug: [https://bugzilla.redhat.com/show_bug.cgi?id=2032639 #2032639]
** Specific changes: (see wiki)

* Current development state can be observed in
[https://copr.fedorainfracloud.org/coprs/pvalena/ruby-on-rails/
pvalena/ruby-on-rails] COPR repository.
** Current status: '''version 7.0.0''' built and tested

* Other developers: Update Rails dependent packages to be working with
Ruby on Rails 7.0
* Policies and guidelines: N/A (not a System Wide Change)
* Trademark approval: N/A (not needed for this Change)

== Upgrade/compatibility impact ==
Web applications build above Ruby on Rails framework might need to be
updated. Official upstream upgrade guide might come handy:
http://guides.rubyonrails.org/upgrading_ruby_on_rails.html

== How To Test ==
* No special hardware is needed.
* Some additional adjustments to dependencies are needed to start the
default app. Example:
** https://github.com/pvalena/theprototype/blob/main/rails/test.sh


=== To test only Rails itself ===

dnf install rubygem-rails
rails new app
cd app && rails s

* Go to http://127.0.0.1:3000/ and make sure you are running Rails 7.0.x

=== To test the complete feature including generating a new Rails app
using RPM ===

dnf group install 'Ruby on Rails'
rails new app --skip-bundle && cd app
rails s

* Go to http://127.0.0.1:3000/ and make sure you are running Rails 7.0.x

== User Experience ==
* New version of Ruby on Rails (7.0) available
* The most significant Rails 7.0 features:
** No-Node default approach to the front end
** Hotwire’s combination of Turbo and Stimulus
** Easily use any JavaScript bundler
** Encrypted attributes in Active Record
** Asynchronous Query Loading
** Zeitwerk autoloader is used exclusively

== Dependencies ==
* There are several packages, which depends on Ruby on Rails framework.
* These needs to be surely updated:
** (none)
* Following gems don't support Rails 7.0 right now and would be broken
by the update:
** (none)
* As Rails requires Ruby >= 2.7, the platform less than the version
can not use Rails 7.0.

== Contingency Plan ==
* Contingency mechanism: None needed. Rails stack won't be updated
until all its dependencies are in Rawhide. After that, it will be a
simple matter of updating the core packages (and their dependencies)
via side-tag.
* Contingency deadline: N/A (not a System Wide Change)
* Blocks release? No
* Blocks product? No

== Documentation ==
* http://api.rubyonrails.org/

== Release Notes ==
* https://rubyonrails.org/2021/12/15/Rails-7-fulfilling-a-vision
* https://edgeguides.rubyonrails.org/7_0_release_notes.html


-- 
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

F36 Change: Wayland by Default for SDDM (Self-Contained Change proposal)

[Ben Cotton]

https://fedoraproject.org/wiki/Changes/WaylandByDefaultForSDDM

= Wayland by Default for SDDM =

== Summary ==
Change the default display server mode for SDDM to use a Wayland-based
greeter rather than an X11-based one.

== Owner ==
* Name: [[User:Ngompa|Neal Gompa]], [[User:Rdieter|Rex Dieter]],
[[User:Jgrulich|Jan Grulich]]
* Email: ngomp...@gmail.com, rdie...@gmail.com, jgrul...@redhat.com
* Product: KDE Spin, Kinoite
* Responsible WG: KDE SIG


== Detailed Description ==
With [https://github.com/sddm/sddm/pull/1393 the work done upstream in
SDDM to support using a Wayland based greeter] and
[[Changes/ReplaceFbdevDrivers|the introduction of SimpleDRM to fix the
broken fallback when platform drivers are unavailable]], it is now
possible for the Fedora KDE variants (the regular spin and Kinoite) to
move to Wayland for the login manager, which effectively completes the
switch to Wayland for these variants.


== Benefit to Fedora ==
As originally detailed in [[Changes/WaylandByDefaultForPlasma|the
Change to switch Plasma to Wayland by default]], Fedora is a leader in
advancing the adoption of the Wayland protocol as part of the overall
strategy to improve the Linux graphical software stack. We have been
successful in helping drive Wayland forward in the Plasma Desktop, and
we intend to do the same for SDDM.

== Scope ==
* Proposal owners:
** Upgrade {{package|sddm}} to the latest snapshot and introduce
mutually exclusive sddm-wayland-generic and
sddm-x11 greeter configuration packages.
** Modify {{package|plasma-workspace}} to switch SDDM to Wayland
*** Enable installation of the SDDM Wayland configuration snippet and
ship as sddm-wayland-plasma that is mutually exclusive
with the other sddm greeter configuration packages. This package will
supplement {{package|sddm}} and plasma-workspace-wayland
to be automatically installed together.
** Modify @kde-desktop comps group for Fedora Linux 36 to
include sddm-wayland-plasma for the media.


* Other developers: N/A (not needed for this Change)

* Release engineering: [https://pagure.io/releng/issue/10536 #10536]
* Policies and guidelines: N/A (not needed for this Change)
* Trademark approval: N/A (not needed for this Change)
* Alignment with Objectives: N/A


== Upgrade/compatibility impact ==
On upgrade to Fedora Linux 36, SDDM will be transparently switched
from the X11 greeter to the Wayland one leveraging kwin. In order to
override this, the user can do one of the following:
* Drop in a configuration file in /etc/sddm.conf.d to set
the display server back to X11
* Swap back to X11 with the configuration package: dnf swap
sddm-wayland-plasma sddm-x11


== How To Test ==
Once the SDDM and Plasma Wayland changes are made, Rawhide users can
try this by using nightly KDE ISOs and using them normally to install
and run a Rawhide KDE Plasma environment.

== User Experience ==
Ideally, there should be no noticeable impact on the user experience,
though users may notice that things operate more smoothly and with
slightly lower resources.

== Dependencies ==
This change is dependent on [[Changes/ReplaceFbdevDrivers|the Change
to replace fbdev with SimpleDRM]]. Without that Change, we will need
to keep SDDM using X11 because otherwise the fallbacks are broken when
drivers do not work.

== Contingency Plan ==
* Contingency mechanism: Update comps and {{package|plasma-workspace}}
so that sddm-x11 is shipped instead.
* Contingency deadline: beta freeze
* Blocks release? Yes


== Documentation ==
N/A (not a System Wide Change)

== Release Notes ==
SDDM, the login manager for the Fedora variants using the KDE Plasma
Desktop, now uses the Wayland display system.


-- 
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

F36 Change: MLT-7 (Self-Contained Change proposal)

[Ben Cotton]

https://fedoraproject.org/wiki/Changes/F36MLT-7

== Summary ==
update MLT to version 7.4 (latest version)

== Owner ==
* Name: [[User:sergiomb| Sérgio Basto]]
* Email: sergi...@fedoraproject.org


== Detailed Description ==
Update of MLT from v6 to v7 breaks the builds, binaries changed the
name and devel files changed the location [1], authors argue that
facilitates have 2 versions of MLT at same time, but I personally
don't want keep to versions of MLT because MLT just 3 or 5 projects
that use it,

[1]
https://github.com/mltframework/mlt/issues/713


== Benefit to Fedora ==
Up-to-date and latest MLT release will be delivered to Fedora users.


== Scope ==
* Proposal owners: [[User:Sergiomb | Sérgio Basto]]
[[https://accounts.fedoraproject.org/user/martinkg/ | Martin
Gansser]]

* Other developers: [[User:Kwizart | Nicolas Chauvet]]
* Release engineering:
* Policies and guidelines: N/A (not needed for this Change)
* Trademark approval: N/A (not needed for this Change)
* Alignment with Objectives:


== Upgrade/compatibility impact ==
We need update ETL , synfig  and synfigstudio  from version 1.40 to
version 1.5.1 .

webvfx (THE PROJECT IS DEPRECATED BY THE MLT TEAM AND NO LONGER
MAINTAINED) we may retire it or build it without MLT support.

== How To Test ==
Run the new synfigstudio and work with it, testing the tasks that user
already did with the previous version

== User Experience ==
They will have updated tools

== Dependencies ==
Already explained on Upgrade/compatibility impact

== Contingency Plan ==

* Contingency mechanism: (What to do?  Who will do it?) (not a System
Wide Change) report upstream and apply fixes ASAP
* Contingency deadline: N/A (not a System Wide Change)
* Blocks release? No

== Documentation ==
https://www.mltframework.org/docs/

== Release Notes ==
post https://www.mltframework.org/blog/v7.0.0_released/

and blog it self https://www.mltframework.org/blog/


-- 
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure