[rpms/perl-Razor-Agent] PR #1: Use make macros

[Tom Stellard]

tstellar opened a new pull-request against the project: `perl-Razor-Agent` that 
you are following:
``
Use make macros
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Razor-Agent/pull-request/1
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[rpms/perl-XML-Parser] PR #1: Use make macros

[Tom Stellard]

tstellar opened a new pull-request against the project: `perl-XML-Parser` that 
you are following:
``
Use make macros
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-XML-Parser/pull-request/1
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[rpms/perl-Digest-MD5] PR #1: Use make macros

[Tom Stellard]

tstellar opened a new pull-request against the project: `perl-Digest-MD5` that 
you are following:
``
Use make macros
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Digest-MD5/pull-request/1
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[rpms/perl-Unicode-Normalize] PR #1: Use make macros

[Tom Stellard]

tstellar opened a new pull-request against the project: 
`perl-Unicode-Normalize` that you are following:
``
Use make macros
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Unicode-Normalize/pull-request/1
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[rpms/perl-MIME-Base64] PR #1: Use make macros

[Tom Stellard]

tstellar opened a new pull-request against the project: `perl-MIME-Base64` that 
you are following:
``
Use make macros
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-MIME-Base64/pull-request/1
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[rpms/perl-Params-Util] PR #1: Use make macros

[Tom Stellard]

tstellar opened a new pull-request against the project: `perl-Params-Util` that 
you are following:
``
Use make macros
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Params-Util/pull-request/1
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[rpms/perl-Compress-Raw-Lzma] PR #1: Use make macros

[Tom Stellard]

tstellar opened a new pull-request against the project: 
`perl-Compress-Raw-Lzma` that you are following:
``
Use make macros
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Compress-Raw-Lzma/pull-request/1
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[rpms/perl-BSD-Resource] PR #1: Use make macros

[Tom Stellard]

tstellar opened a new pull-request against the project: `perl-BSD-Resource` 
that you are following:
``
Use make macros
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-BSD-Resource/pull-request/1
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[389-devel] 389 DS nightly 2020-07-21 - 95% PASS

[vashirov]

https://fedorapeople.org/groups/389ds/ci/nightly/2020/07/21/report-389-ds-base-1.4.4.4-20200720git22c5149.fc32.x86_64.html
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org

[Bug 1854753] perl-Sereal-4.015 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version|perl-Sereal-4.015-1.fc33|perl-Sereal-4.015-1.fc33
   |perl-Sereal-4.017-1.fc32|perl-Sereal-4.017-1.fc32
   ||perl-Sereal-4.017-1.fc31



--- Comment #15 from Fedora Update System  ---
FEDORA-2020-1f18f358d0 has been pushed to the Fedora 31 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.
___
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

[Bug 1854754] perl-Sereal-Decoder-4.015 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version|perl-Sereal-Decoder-4.015-1 |perl-Sereal-Decoder-4.015-1
   |.fc33   |.fc33
   |perl-Sereal-Decoder-4.017-1 |perl-Sereal-Decoder-4.017-1
   |.fc32   |.fc32
   ||perl-Sereal-Decoder-4.017-1
   ||.fc31



--- Comment #15 from Fedora Update System  ---
FEDORA-2020-1f18f358d0 has been pushed to the Fedora 31 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.
___
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

[Bug 1855333] perl-Sereal-Decoder-4.017 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version|perl-Sereal-Decoder-4.017-1 |perl-Sereal-Decoder-4.017-1
   |.fc33   |.fc33
   |perl-Sereal-Decoder-4.017-1 |perl-Sereal-Decoder-4.017-1
   |.fc32   |.fc32
   ||perl-Sereal-Decoder-4.017-1
   ||.fc31



--- Comment #13 from Fedora Update System  ---
FEDORA-2020-1f18f358d0 has been pushed to the Fedora 31 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.
___
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

[Bug 1855332] perl-Sereal-4.017 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version|perl-Sereal-4.017-1.fc33|perl-Sereal-4.017-1.fc33
   |perl-Sereal-4.017-1.fc32|perl-Sereal-4.017-1.fc32
   ||perl-Sereal-4.017-1.fc31



--- Comment #13 from Fedora Update System  ---
FEDORA-2020-1f18f358d0 has been pushed to the Fedora 31 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.
___
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

[Bug 1854752] perl-Sereal-Encoder-4.015 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version|perl-Sereal-Encoder-4.015-1 |perl-Sereal-Encoder-4.015-1
   |.fc33   |.fc33
   |perl-Sereal-Encoder-4.017-1 |perl-Sereal-Encoder-4.017-1
   |.fc32   |.fc32
   ||perl-Sereal-Encoder-4.017-1
   ||.fc31



--- Comment #15 from Fedora Update System  ---
FEDORA-2020-1f18f358d0 has been pushed to the Fedora 31 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.
___
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

[Bug 1855334] perl-Sereal-Encoder-4.017 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version|perl-Sereal-Encoder-4.017-1 |perl-Sereal-Encoder-4.017-1
   |.fc33   |.fc33
   |perl-Sereal-Encoder-4.017-1 |perl-Sereal-Encoder-4.017-1
   |.fc32   |.fc32
   ||perl-Sereal-Encoder-4.017-1
   ||.fc31



--- Comment #13 from Fedora Update System  ---
FEDORA-2020-1f18f358d0 has been pushed to the Fedora 31 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.
___
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

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

[updates]

The following Fedora EPEL 8 Security updates need testing:
 Age  URL
  12  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-ff58160b15   
libslirp-4.3.1-1.el8
  12  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-672e6676c7   
seamonkey-2.53.3-1.el8
   6  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-12d0e14fab   
cacti-1.2.13-1.el8 cacti-spine-1.2.13-1.el8
   6  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-1c906e59bb   
mbedtls-2.16.7-1.el8
   6  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-442e619b4a   
singularity-3.6.0-1.el8
   4  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-31b5963358   
tor-0.4.3.6-1.el8
   4  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-a0f28fffcf   
bashtop-0.9.24-1.el8
   3  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-cf34e230c7   
clamav-0.102.4-1.el8


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

dkms-2.8.3-2.el8
matio-1.5.17-3.el8
netdata-1.23.2-1.el8
python-colcon-core-0.6.0-1.el8
python-colcon-mixin-0.2.0-1.el8
python-colcon-package-selection-0.2.8-1.el8
python-colcon-python-setup-py-0.2.6-1.el8
python-colcon-ros-0.3.19-1.el8
wsdd-0.6.1-2.el8

Details about builds:



 dkms-2.8.3-2.el8 (FEDORA-EPEL-2020-2a4c2c399e)
 Dynamic Kernel Module Support Framework

Update Information:

Update to 2.8.2 with kernel module signing option.

ChangeLog:

* Mon Jul 20 2020 Simone Caronni  - 2.8.3-2
- Add make to requirements.
* Wed Jul 15 2020 Simone Caronni  - 2.8.3-1
- Update to 2.8.3.
* Thu Jul  2 2020 Simone Caronni  - 2.8.2-1
- Update to 2.8.2.
- Add sign helper script sample to docs.

References:

  [ 1 ] Bug #1767313 - dkms-2.8.2 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1767313
  [ 2 ] Bug #1803415 - DKMS runs on reboot instead of as hook
https://bugzilla.redhat.com/show_bug.cgi?id=1803415
  [ 3 ] Bug #1829021 - Error! Bad return status for module build on kernel: 
5.6.6-200.fc31.x86_64 (x86_64)
https://bugzilla.redhat.com/show_bug.cgi?id=1829021




 matio-1.5.17-3.el8 (FEDORA-EPEL-2020-fcbe2aa222)
 Library for reading/writing Matlab MAT files

Update Information:

Initial package for EPEL8

ChangeLog:


References:

  [ 1 ] Bug #1757289 - Please build matio for EPEL-8
https://bugzilla.redhat.com/show_bug.cgi?id=1757289




 netdata-1.23.2-1.el8 (FEDORA-EPEL-2020-f430b9d32d)
 Real-time performance monitoring

Update Information:

Update from upstream

ChangeLog:

* Fri Jul 17 2020 Didier Fabert  1.23.2-1
- Update from upstream

References:

  [ 1 ] Bug #1851012 - netdata-1.23.1 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1851012




 python-colcon-core-0.6.0-1.el8 (FEDORA-EPEL-2020-c30b74ad83)
 Command line tool to build sets of software packages

Update Information:

Update to the latest colcon package releases

ChangeLog:

* Mon Jul 20 2020 Scott K Logan  - 0.6.0-1
- Update to 0.6.0 (rhbz#1858471)

References:

  [ 1 ] Bug #1858470 - python-colcon-mixin-0.2.0 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1858470
  [ 2 ] Bug #1858471 - python-colcon-core-0.6.0 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1858471
  [ 3 ] Bug #1858472 - python-colcon-ros-0.3.19 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1858472
  [ 4 ] Bug #1858473 - python-colcon-python-setup-py-0.2.6 is available

[Bug 1858528] perl-File-Path-2.17 is available

[bugzilla]

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



--- Comment #5 from Fedora Update System  ---
FEDORA-2020-1845580db2 has been pushed to the Fedora 31 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing
--advisory=FEDORA-2020-1845580db2`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-1845580db2

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

[Bug 1858476] perl-CPAN-Perl-Releases-5.20200717 is available

[bugzilla]

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



--- Comment #5 from Fedora Update System  ---
FEDORA-2020-85392ab421 has been pushed to the Fedora 31 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing
--advisory=FEDORA-2020-85392ab421`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-85392ab421

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

[Bug 1858467] perl-Compress-Bzip2-2.28 is available

[bugzilla]

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



--- Comment #4 from Fedora Update System  ---
FEDORA-2020-7483c5007e has been pushed to the Fedora 31 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing
--advisory=FEDORA-2020-7483c5007e`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-7483c5007e

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

[Bug 1858481] perl-Module-CoreList-5.20200717 is available

[bugzilla]

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



--- Comment #5 from Fedora Update System  ---
FEDORA-2020-c802fdad2e has been pushed to the Fedora 31 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing
--advisory=FEDORA-2020-c802fdad2e`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-c802fdad2e

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

[Bug 1840363] perl-Compress-Bzip2-2.27 is available

[bugzilla]

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



--- Comment #13 from Fedora Update System  ---
FEDORA-2020-7483c5007e has been pushed to the Fedora 31 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing
--advisory=FEDORA-2020-7483c5007e`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-7483c5007e

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

[Bug 1857787] perl-LWP-Protocol-https-6.09 is available

[bugzilla]

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



--- Comment #6 from Fedora Update System  ---
FEDORA-2020-ca566ca0df has been pushed to the Fedora 31 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing
--advisory=FEDORA-2020-ca566ca0df`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-ca566ca0df

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

[Bug 1858528] perl-File-Path-2.17 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #4 from Fedora Update System  ---
FEDORA-2020-2846760782 has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing
--advisory=FEDORA-2020-2846760782`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-2846760782

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

[Bug 1858481] perl-Module-CoreList-5.20200717 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #4 from Fedora Update System  ---
FEDORA-2020-20b70fc964 has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing
--advisory=FEDORA-2020-20b70fc964`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-20b70fc964

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

[Bug 1857787] perl-LWP-Protocol-https-6.09 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #5 from Fedora Update System  ---
FEDORA-2020-949a75223b has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing
--advisory=FEDORA-2020-949a75223b`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-949a75223b

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

[Bug 1858467] perl-Compress-Bzip2-2.28 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #3 from Fedora Update System  ---
FEDORA-2020-ccb3c84ade has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing
--advisory=FEDORA-2020-ccb3c84ade`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-ccb3c84ade

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

[Bug 1858476] perl-CPAN-Perl-Releases-5.20200717 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #4 from Fedora Update System  ---
FEDORA-2020-6327f493e8 has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing
--advisory=FEDORA-2020-6327f493e8`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-6327f493e8

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

[Bug 1854754] perl-Sereal-Decoder-4.015 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ON_QA   |CLOSED
   Fixed In Version|perl-Sereal-Decoder-4.015-1 |perl-Sereal-Decoder-4.015-1
   |.fc33   |.fc33
   ||perl-Sereal-Decoder-4.017-1
   ||.fc32
 Resolution|--- |ERRATA
Last Closed||2020-07-21 01:03:01



--- Comment #14 from Fedora Update System  ---
FEDORA-2020-43a6a0fdca has been pushed to the Fedora 32 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.
___
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

[Bug 1854753] perl-Sereal-4.015 is available

[bugzilla]

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

Bug 1854754 Summary: perl-Sereal-Decoder-4.015 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1854754

   What|Removed |Added

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




-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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

[Bug 1855332] perl-Sereal-4.017 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ON_QA   |CLOSED
   Fixed In Version|perl-Sereal-4.017-1.fc33|perl-Sereal-4.017-1.fc33
   ||perl-Sereal-4.017-1.fc32
 Resolution|--- |ERRATA
Last Closed||2020-07-21 01:03:04



--- Comment #12 from Fedora Update System  ---
FEDORA-2020-43a6a0fdca has been pushed to the Fedora 32 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.
___
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

[Bug 1854752] perl-Sereal-Encoder-4.015 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ON_QA   |CLOSED
   Fixed In Version|perl-Sereal-Encoder-4.015-1 |perl-Sereal-Encoder-4.015-1
   |.fc33   |.fc33
   ||perl-Sereal-Encoder-4.017-1
   ||.fc32
 Resolution|--- |ERRATA
Last Closed||2020-07-21 01:02:57



--- Comment #14 from Fedora Update System  ---
FEDORA-2020-43a6a0fdca has been pushed to the Fedora 32 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.
___
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

[Bug 1855333] perl-Sereal-Decoder-4.017 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ON_QA   |CLOSED
   Fixed In Version|perl-Sereal-Decoder-4.017-1 |perl-Sereal-Decoder-4.017-1
   |.fc33   |.fc33
   ||perl-Sereal-Decoder-4.017-1
   ||.fc32
 Resolution|--- |ERRATA
Last Closed||2020-07-21 01:03:06



--- Comment #12 from Fedora Update System  ---
FEDORA-2020-43a6a0fdca has been pushed to the Fedora 32 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.
___
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

[Bug 1854753] perl-Sereal-4.015 is available

[bugzilla]

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

Bug 1854752 Summary: perl-Sereal-Encoder-4.015 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1854752

   What|Removed |Added

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




-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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

[Bug 1854753] perl-Sereal-4.015 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ON_QA   |CLOSED
   Fixed In Version|perl-Sereal-4.015-1.fc33|perl-Sereal-4.015-1.fc33
   ||perl-Sereal-4.017-1.fc32
 Resolution|--- |ERRATA
Last Closed||2020-07-21 01:02:59



--- Comment #14 from Fedora Update System  ---
FEDORA-2020-43a6a0fdca has been pushed to the Fedora 32 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.
___
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

[Bug 1855334] perl-Sereal-Encoder-4.017 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ON_QA   |CLOSED
   Fixed In Version|perl-Sereal-Encoder-4.017-1 |perl-Sereal-Encoder-4.017-1
   |.fc33   |.fc33
   ||perl-Sereal-Encoder-4.017-1
   ||.fc32
 Resolution|--- |ERRATA
Last Closed||2020-07-21 01:03:08



--- Comment #12 from Fedora Update System  ---
FEDORA-2020-43a6a0fdca has been pushed to the Fedora 32 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.
___
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

[Bug 1858788] ddclient dependency missing

[bugzilla]

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



--- Comment #5 from Scott Talbert  ---
This should be fixed whenever the next epel8-playground compose runs.  Please
check in a day or so.

Sorry for my rush to close.  I get a lot of bug reports for ddclient where
people haven't enabled PowerTools and there's a different perl package
dependency missing.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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

[Bug 1850795] Add perl-DateTimeX-Easy to EPEL8 / co-maintainer request

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ON_QA   |CLOSED
 Resolution|--- |ERRATA
Last Closed||2020-07-21 00:25:43



--- Comment #5 from Fedora Update System  ---
FEDORA-EPEL-2020-290e37916e 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.
___
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

[Bug 1850776] Add perl-MooseX-Types-DateTime-MoreCoercions to EPEL8

[bugzilla]

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

Bug 1850795 Summary: Add perl-DateTimeX-Easy to EPEL8 / co-maintainer request
https://bugzilla.redhat.com/show_bug.cgi?id=1850795

   What|Removed |Added

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




-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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

Re: gdb says "Unexpected size of section `.reg-xstate/...` in core file

[Kevin Buettner]

On Sat, 11 Jul 2020 14:52:41 +
Zbigniew J__drzejewski-Szmek  wrote:

> I'm not sure if this is a bug and if it is, where it is...
> 
> $ coredumpctl gdb
> ...
> Using host libthread_db library "/lib64/libthread_db.so.1".
> Core was generated by `/usr/lib/systemd/systemd-oomd'.
> Program terminated with signal SIGABRT, Aborted.
> 
> warning: Unexpected size of section `.reg-xstate/59286' in core file.
> #0  0x7f552f8b3b95 in raise () from /lib64/libc.so.6
> (gdb)
> 
> Is this gcc, gdb, binutils, something else?

I think this is the same problem that I encountered recently.  If
so, it turned out to be a kernel bug.

See:

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

Kevin
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Unexpected package disappearance on Rawhide

[Miro Hrončok]

On 21. 07. 20 1:36, Mohamed El Morabity wrote:

Hello,

I'm maintaining the python-azure-sdk package. I updated it 3 weeks ago to solve 
install dependencies issues on F32 and Rawhide. It built successfully for both 
these Fedora releases, the corresponding updates appeared on Bodhi 
(https://bodhi.fedoraproject.org/updates/FEDORA-2020-db2801a270 for Rawhide) and 
the update is now in stable for F32.


Unfortunately it looks like my build never hit Rawhide repositories. It even 
seems the package has disappeared from Rawhide:

   $ dnf list python3-azure-sdk
   Last metadata expiration check: 0:17:28 ago on Mon Jul 20 23:08:08 2020.
   Error: No matching Packages to list

I thought about rebuilding the package... Pushes are denied:
   $ LANG=C fedpkg push
   [...]
   remote: Branch refs/heads/master is unsupported
   remote: Denied push for ref 'refs/heads/master' for user 'melmorabity'
   remote: All changes have been rejected
   To ssh://pkgs.fedoraproject.org/rpms/python-azure-sdk 


    ! [remote rejected] master -> master (pre-receive hook declined)
   error: failed to push some refs to 
'ssh://melmorab...@pkgs.fedoraproject.org/rpms/python-azure-sdk 
'

   Could not execute push: Failed to execute command.

I don't recall my package was orphaned for lack of maintenance or such.

Any clues about this issue?


$ koji list-pkgs  --show-blocked --tag f33 --quiet --package python-azure-sdk
python-azure-sdkf33  releng 
[BLOCKED]



The package appears to be in retired state, but it was not retired in git. I 
suggest opening a ticket at https://pagure.io/releng/issues


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

Unexpected package disappearance on Rawhide

[Mohamed El Morabity]

Hello,

I'm maintaining the python-azure-sdk package. I updated it 3 weeks ago to
solve install dependencies issues on F32 and Rawhide. It built successfully
for both these Fedora releases, the corresponding updates appeared on Bodhi
(https://bodhi.fedoraproject.org/updates/FEDORA-2020-db2801a270 for
Rawhide) and the update is now in stable for F32.

Unfortunately it looks like my build never hit Rawhide repositories. It
even seems the package has disappeared from Rawhide:
  $ dnf list python3-azure-sdk
  Last metadata expiration check: 0:17:28 ago on Mon Jul 20 23:08:08 2020.
  Error: No matching Packages to list

I thought about rebuilding the package... Pushes are denied:
  $ LANG=C fedpkg push
  [...]
  remote: Branch refs/heads/master is unsupported
  remote: Denied push for ref 'refs/heads/master' for user 'melmorabity'
  remote: All changes have been rejected
  To ssh://pkgs.fedoraproject.org/rpms/python-azure-sdk
   ! [remote rejected] master -> master (pre-receive hook declined)
  error: failed to push some refs to 'ssh://
melmorab...@pkgs.fedoraproject.org/rpms/python-azure-sdk'
  Could not execute push: Failed to execute command.

I don't recall my package was orphaned for lack of maintenance or such.

Any clues about this issue?

Best regards,
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Fedora 33 Mass Rebuild

[Mohan Boddu]

Mohan Boddu 

4:32 PM (1 hour ago)
to devel-announce
Hi all,

Per the Fedora 33 schedule[1] we will start a mass rebuild for Fedora 33
on Jul 22nd 2020. We will run a mass rebuild for Fedora 33 for the
changes listed in:

https://pagure.io/releng/issues?status=Open=mass+rebuild

Mass rebuild will be done in a side tag (f33-rebuild) and moved over
when completed.

Failures can be seen
https://kojipkgs.fedoraproject.org/mass-rebuild/f33-failures.html

Things still needing rebuilt
https://kojipkgs.fedoraproject.org/mass-rebuild/f33-need-rebuild.html

FTBFS bugs will be filed shortly.

Please be sure to let releng know if you see any bugs in the
reporting. You can contact releng in #fedora-releng on freenode, by
dropping an email to our list[2] or filing an issue in pagure[3]

Regards,
Mohan Boddu.

[1] https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html
[2] https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/
[3] https://pagure.io/releng/
___
devel-announce mailing list -- devel-annou...@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org
___
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

List of long term FTBFS packages to be retired in August

[Miro Hrončok]

Dear maintainers.

Based on the current fail to build from source policy, the following packages
will be retired from Fedora 33 approximately one week before branching (August 
2020).


Policy: 
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/


Note that some listed packages are orphaned and hence may be retired even 
sooner.

The packages in rawhide were not successfully built at least since Fedora 31.

This report is based on dist tags.

Packages collected via:
https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ftbfs-retirements.ipynb

If you see a package that was built, please let me know.
If you see a package that should be exempted from the process, please let me 
know and we can work together to get a FESCo approval for that.


If you see a package that can be rebuilt, please do so.


   Package (co)maintainers  Latest build

OpenCoarrays   jussilehtola Fedora 30
js-jquery-jqplot   xavierb  Fedora 30
js-jquery1 nodejs-sig, patches, vondruchFedora 30
js-jquery2 vondruch Fedora 30
js-sizzle  nodejs-sig, patches, vondruchFedora 30
nodejs-path-type   nodejs-sig, orphan   Fedora 30
nodejs-temp-write  orphan   Fedora 30
nodejs-unique-stream   jsmith, nodejs-sig   Fedora 30
orpie  bowlofeggs, orphan   Fedora 30
rubygem-ruby-hmac  humaton, mmorsi  Fedora 30


The following packages require above mentioned packages:
Depending on: js-jquery-jqplot (1)
sympa (maintained by: xavierb)
sympa-6.2.56-1.fc33.src requires js-jquery-jqplot = 1.0.9-3.fc30
sympa-6.2.56-1.fc33.x86_64 requires js-jquery-jqplot = 
1.0.9-3.fc30

Depending on: js-jquery1 (70)
R-profvis (maintained by: qulogic)
R-profvis-0.3.6-3.fc33.src requires js-jquery1 = 1.12.4-7.fc30
R-profvis-0.3.6-3.fc33.x86_64 requires js-jquery1 = 
1.12.4-7.fc30

R-rmarkdown (maintained by: qulogic)
R-rmarkdown-2.2-1.fc33.noarch requires js-jquery1 = 
1.12.4-7.fc30
R-rmarkdown-2.2-1.fc33.src requires js-jquery1 = 1.12.4-7.fc30

copr-frontend (maintained by: clime, copr-sig, dturecek, frostyx, 
msuchy, praiskup)
copr-frontend-1.166-1.fc33.noarch requires js-jquery1 = 
1.12.4-7.fc30

ghc-pretty-show (maintained by: mathstuf)
ghc-pretty-show-1.9.5-3.fc32.x86_64 requires js-jquery1 = 
1.12.4-7.fc30

mkdocs (maintained by: cheeselee)
mkdocs-1.1.2-1.fc33.noarch requires js-jquery1 = 1.12.4-7.fc30
mkdocs-1.1.2-1.fc33.src requires js-jquery1 = 1.12.4-7.fc30

python-XStatic-jQuery (maintained by: mrunge, openstack-sig, rdopiera)
python3-XStatic-jQuery-3.4.1.0-2.fc33.noarch requires 
js-jquery1 = 1.12.4-7.fc30

python-sphinx-bootstrap-theme (maintained by: besser82, sic)
		python3-sphinx-bootstrap-theme-0.8.0-3.fc33.noarch requires js-jquery1 = 
1.12.4-7.fc30


rubygem-apipie-rails (maintained by: jaruga, ruby-packagers-sig, 
vondruch)
rubygem-apipie-rails-0.5.5-6.fc32.noarch requires js-jquery1 = 
1.12.4-7.fc30

R-BiocFileCache (maintained by: spot)
R-BiocFileCache-1.12.0-2.fc33.src requires R-rmarkdown = 
2.2-1.fc33

R-DBItest (maintained by: qulogic)
R-DBItest-1.7.0-1.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-V8 (maintained by: qulogic)
R-V8-3.1.0-3.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-broom (maintained by: qulogic)
R-broom-0.5.6-2.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-cellranger (maintained by: qulogic)
R-cellranger-1.1.0-6.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-clipr (maintained by: qulogic)
R-clipr-0.7.0-3.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-dbplyr (maintained by: qulogic)
R-dbplyr-1.4.3-2.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-devtools (maintained by: qulogic)
R-devtools-2.1.0-2.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-diffobj (maintained by: qulogic)
R-diffobj-0.3.0-2.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-dplyr (maintained by: qulogic)
R-dplyr-0.8.5-2.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-dtplyr (maintained by: qulogic)
R-dtplyr-1.0.1-2.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-foghorn (maintained by: qulogic)
R-foghorn-1.1.0-5.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-forcats (maintained by: qulogic)
R-forcats-0.5.0-2.fc33.src requires R-rmarkdown = 

Fedora 33 Mass Rebuild

[Mohan Boddu]

Mohan Boddu 

4:32 PM (1 hour ago)
to devel-announce
Hi all,

Per the Fedora 33 schedule[1] we will start a mass rebuild for Fedora 33
on Jul 22nd 2020. We will run a mass rebuild for Fedora 33 for the
changes listed in:

https://pagure.io/releng/issues?status=Open=mass+rebuild

Mass rebuild will be done in a side tag (f33-rebuild) and moved over
when completed.

Failures can be seen
https://kojipkgs.fedoraproject.org/mass-rebuild/f33-failures.html

Things still needing rebuilt
https://kojipkgs.fedoraproject.org/mass-rebuild/f33-need-rebuild.html

FTBFS bugs will be filed shortly.

Please be sure to let releng know if you see any bugs in the
reporting. You can contact releng in #fedora-releng on freenode, by
dropping an email to our list[2] or filing an issue in pagure[3]

Regards,
Mohan Boddu.

[1] https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html
[2] https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/
[3] https://pagure.io/releng/
___
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

List of long term FTBFS packages to be retired in August

[Miro Hrončok]

Dear maintainers.

Based on the current fail to build from source policy, the following packages
will be retired from Fedora 33 approximately one week before branching (August 
2020).


Policy: 
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/


Note that some listed packages are orphaned and hence may be retired even 
sooner.

The packages in rawhide were not successfully built at least since Fedora 31.

This report is based on dist tags.

Packages collected via:
https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ftbfs-retirements.ipynb

If you see a package that was built, please let me know.
If you see a package that should be exempted from the process, please let me 
know and we can work together to get a FESCo approval for that.


If you see a package that can be rebuilt, please do so.


   Package (co)maintainers  Latest build

OpenCoarrays   jussilehtola Fedora 30
js-jquery-jqplot   xavierb  Fedora 30
js-jquery1 nodejs-sig, patches, vondruchFedora 30
js-jquery2 vondruch Fedora 30
js-sizzle  nodejs-sig, patches, vondruchFedora 30
nodejs-path-type   nodejs-sig, orphan   Fedora 30
nodejs-temp-write  orphan   Fedora 30
nodejs-unique-stream   jsmith, nodejs-sig   Fedora 30
orpie  bowlofeggs, orphan   Fedora 30
rubygem-ruby-hmac  humaton, mmorsi  Fedora 30


The following packages require above mentioned packages:
Depending on: js-jquery-jqplot (1)
sympa (maintained by: xavierb)
sympa-6.2.56-1.fc33.src requires js-jquery-jqplot = 1.0.9-3.fc30
sympa-6.2.56-1.fc33.x86_64 requires js-jquery-jqplot = 
1.0.9-3.fc30

Depending on: js-jquery1 (70)
R-profvis (maintained by: qulogic)
R-profvis-0.3.6-3.fc33.src requires js-jquery1 = 1.12.4-7.fc30
R-profvis-0.3.6-3.fc33.x86_64 requires js-jquery1 = 
1.12.4-7.fc30

R-rmarkdown (maintained by: qulogic)
R-rmarkdown-2.2-1.fc33.noarch requires js-jquery1 = 
1.12.4-7.fc30
R-rmarkdown-2.2-1.fc33.src requires js-jquery1 = 1.12.4-7.fc30

copr-frontend (maintained by: clime, copr-sig, dturecek, frostyx, 
msuchy, praiskup)
copr-frontend-1.166-1.fc33.noarch requires js-jquery1 = 
1.12.4-7.fc30

ghc-pretty-show (maintained by: mathstuf)
ghc-pretty-show-1.9.5-3.fc32.x86_64 requires js-jquery1 = 
1.12.4-7.fc30

mkdocs (maintained by: cheeselee)
mkdocs-1.1.2-1.fc33.noarch requires js-jquery1 = 1.12.4-7.fc30
mkdocs-1.1.2-1.fc33.src requires js-jquery1 = 1.12.4-7.fc30

python-XStatic-jQuery (maintained by: mrunge, openstack-sig, rdopiera)
python3-XStatic-jQuery-3.4.1.0-2.fc33.noarch requires 
js-jquery1 = 1.12.4-7.fc30

python-sphinx-bootstrap-theme (maintained by: besser82, sic)
		python3-sphinx-bootstrap-theme-0.8.0-3.fc33.noarch requires js-jquery1 = 
1.12.4-7.fc30


rubygem-apipie-rails (maintained by: jaruga, ruby-packagers-sig, 
vondruch)
rubygem-apipie-rails-0.5.5-6.fc32.noarch requires js-jquery1 = 
1.12.4-7.fc30

R-BiocFileCache (maintained by: spot)
R-BiocFileCache-1.12.0-2.fc33.src requires R-rmarkdown = 
2.2-1.fc33

R-DBItest (maintained by: qulogic)
R-DBItest-1.7.0-1.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-V8 (maintained by: qulogic)
R-V8-3.1.0-3.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-broom (maintained by: qulogic)
R-broom-0.5.6-2.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-cellranger (maintained by: qulogic)
R-cellranger-1.1.0-6.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-clipr (maintained by: qulogic)
R-clipr-0.7.0-3.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-dbplyr (maintained by: qulogic)
R-dbplyr-1.4.3-2.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-devtools (maintained by: qulogic)
R-devtools-2.1.0-2.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-diffobj (maintained by: qulogic)
R-diffobj-0.3.0-2.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-dplyr (maintained by: qulogic)
R-dplyr-0.8.5-2.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-dtplyr (maintained by: qulogic)
R-dtplyr-1.0.1-2.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-foghorn (maintained by: qulogic)
R-foghorn-1.1.0-5.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-forcats (maintained by: qulogic)
R-forcats-0.5.0-2.fc33.src requires R-rmarkdown = 

Re: How do Fedora developers get access to devtoolset for testing.

[Jonathan Wakely]

On 21/07/20 00:00 +0200, Kevin Kofler wrote:

Steven Munroe wrote:

$ sudo dnf install devtoolset-9-gcc-9.3.1-2.el7.ppc64le.rpm
devtoolset-9-gcc-c++-9.3.1-2.el7.ppc64le.rpm
devtoolset-9-runtime-9.1-0.el7.ppc64le.rpm
devtoolset-9-libstdc++-devel-9.3.1-2.el7.ppc64le.rpm


Installing individual RPMs is a bad idea, because it means you have to
resolve all dependencies manually. Instead, you need to set up the linked
repository as a repository, then just sudo dnf install devtoolset-9-gcc-c++
and it will drag in everything it needs.


Or just stop trying to install devtoolset on Fedora.

___
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

Re: How do Fedora developers get access to devtoolset for testing.

[Jonathan Wakely]

On 20/07/20 16:01 -0500, Steven Munroe wrote:

Jonathan Wakely wrote:

Why are you asking fedpkg to build for f33 if you are trying to
package something for el7 and el8?


I am trying to get better turn around for myself as I have local
access to a POWER8 machine. And I was having difficulty debug the
weird failure I was seeing.


Use mock to get a clean el7 build environment on the POWER8 machine.


That submits a build to koji, to build it using the packages
available in the f33 buildroot.


Yup "fedpkg --release epel7 scratch-build".  was also failing because
of some difference in the spelling of "*debug" files, that was unique
to el7 required a change in the spec file. A local build would have
been a lot quicker than koji


Maybe if it was possible, yes. But it's not possible without heroic
effort, and even then you'll have a mishmash of incompatible packages.
That's not reproducable or reliable or sensible.

The way to workaround a failure on --release epel7 builds is not to
turn your local system into something that is neither f33 nor epel7.



There are several ways to build for el7 or el8:


That helps thanks.


What you're trying to do now seems to be to create a
frankenstein system containing bits of fedora and bits of el7,


Well to me devtoolset looks a lot like the Advance Toolchain which I
have been using on Linux since 2013 It is available  on various
distros including Ubuntu and Fedora.


That doesn't mean you can install it on Fedora though.

The point of devtoolset is to get newer versions of toolchain packages
on RHEL and CentOS. There is no advantage to installing it on Fedora,
because Fedora already *has* newer toolchain pieces. Even newer than
are in the latest devtoolset releases. It could be made to work, but
would be pointless, and the devtoolset maintainers are not going to
invest their time in making it work. So you'd have to spend your time
doing a completely pointless port of devtoolset to Fedora, just to
enable you to do something ill-advised in the first place.

___
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

Re: How do Fedora developers get access to devtoolset for testing.

[Kevin Kofler]

Steven Munroe wrote:
> $ sudo dnf install devtoolset-9-gcc-9.3.1-2.el7.ppc64le.rpm
> devtoolset-9-gcc-c++-9.3.1-2.el7.ppc64le.rpm
> devtoolset-9-runtime-9.1-0.el7.ppc64le.rpm
> devtoolset-9-libstdc++-devel-9.3.1-2.el7.ppc64le.rpm

Installing individual RPMs is a bad idea, because it means you have to 
resolve all dependencies manually. Instead, you need to set up the linked 
repository as a repository, then just sudo dnf install devtoolset-9-gcc-c++ 
and it will drag in everything it needs.

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

Re: How do Fedora developers get access to devtoolset for testing.

[Steven Munroe]

Jonathan Wakely wrote:
> Why are you asking fedpkg to build for f33 if you are trying to
> package something for el7 and el8?

I am trying to get better turn around for myself as I have local
access to a POWER8 machine. And I was having difficulty debug the
weird failure I was seeing.

> That submits a build to koji, to build it using the packages
> available in the f33 buildroot.

Yup "fedpkg --release epel7 scratch-build".  was also failing because
of some difference in the spelling of "*debug" files, that was unique
to el7 required a change in the spec file. A local build would have
been a lot quicker than koji

> There are several ways to build for el7 or el8:

That helps thanks.

> What you're trying to do now seems to be to create a
> frankenstein system containing bits of fedora and bits of el7,

Well to me devtoolset looks a lot like the Advance Toolchain which I
have been using on Linux since 2013 It is available  on various
distros including Ubuntu and Fedora.
___
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

F33 Change proposal: Stratis 2.1.0 (Self-Contained Change)

[Ben Cotton]

https://fedoraproject.org/wiki/Changes/Stratis_2.1.0

= Stratis 2.1.0 =

== Summary ==
Stratis now supports per-pool encryption of the devices that form a pool's
data tier. A pool may be encrypted, or its constituent encrypted devices
may be activated, by means of a key stored in the kernel keyring.

== Owner ==
* Name: [[User:dkeefe|Dennis Keefe]], [[User:mulhern|Anne Mulhern]],
[[User:jbaublitz|John Baublitz]]
* Email: dke...@redhat.com, amulh...@redhat.com, jbaubl...@redhat.com

== Detailed Description ==
=== Stratis 2.1.0 introduces support for encryption. ===

It supports per-pool encryption of the devices that form a pool's data
tier. A pool may be encrypted, or its constituent encrypted devices may be
activated, by means of a key stored in the kernel keyring.

=== stratisd 2.1.0 ===
This release implements encryption support and adds several new D-Bus
interfaces to administer or monitor that support.

It implements encryption support in the following way:

* A single instance of stratisd can support both encrypted and unencrypted
pools.
The choice to encrypt a pool must be made at the time a pool is created.

* At present, the use of a cache and of encryption are mutually exclusive;
if the pool is created with encryption enabled, then it is not possible to
create a cache.

* Each pool may be encrypted by means of a key in the kernel keyring; each
encrypted pool may make use of a different key, but all devices in a pool
are encrypted with a single key.

* Any additional devices that are added to an encrypted pool's data tier
will be encrypted using the key that was specified when the pool was
initialized.

=== stratisd 2.1.0 supplies several new D-Bus interfaces: ===

* org.storage.stratis2.manager.r1: This interface supplies an extended
CreatePool method, to support an optional argument for encryption. In
addition, it supplies a number of methods for key management.

* org.storage.stratis2.pool.r1: This interface supports explicit
initialization of a cache tier. Previously, a cache was initialized as a
side-effect of the addition of the first device to the cache tier. It also
supports the new Encrypted property.

* org.storage.stratis2.FetchProperties.r1: This interface supports an
additional HasCache property.

* org.storage.stratis2.Report.r1: This interface supports a set of ad-hoc
reports about Stratis. The interface is unstable; the names by which the
reports can be accesed are not guaranteed to remain stable, and the format
of any report is only guaranteed to be valid JSON.

Please consult the D-Bus API Reference for the precise D-Bus specification.

The following are significant implementation details:

* Each block device in an encrypted pool's data tier is encrypted with a
distinct, randomly chosen MEK (Media Encryption Key) on initialization.

* All devices belonging to a single encrypted pool share a single
passphrase, supplied via the kernel keyring.

* The release requires cryptsetup version 2.3.

=== stratis-cli 2.1.0 ===
This release requires stratisd 2.1.0. The user will observe the following
changes:

* The pool create command has been extended to allow encryption.

* There is a new pool init_cache command for initializing a cache.

* There is a new subcommand, key, for key management tasks.

* There is a new subcommand, report, which allows the display of certain
reports generated by stratisd.

* The output of pool list now includes a Properties column; each entry in
the column is a string encoding the following properties of the pool: (1)
whether or not it has a cache, (2) whether or not it is encrypted.

* All commands now verify that stratis is communicating with a compatible
version of stratisd and will fail with an appropriate error if stratisd is
found to have an incompatible version.

=== Usage ===
To create an encrypted pool, a user must first ensure that a key is placed
in the kernel keyring. We strongly encourage using the commands available
via the stratis "key" subcommand for this task. This key, which is secret,
has a corresponding key description, which is public.

An encrypted pool is then created by specifying the key description when
using the pool create command.

It is necessary that the correct key and corresponding key description be
set in the kernel keyring in order to set up a previously encrypted pool.
Setting up a previously encrypted pool requires an explicit pool unlock
command from the user. This command will attempt to unlock the devices
belonging to any previously encrypted pool; it can only unlock all devices
if a key for every encrypted pool is in the keyring. Once the devices
belonging to a previously encrypted pool have been unlocked, the pool will
be set up, and can be used in exactly the same manner as an unencrypted
pool.

== Feedback ==

== Benefits to Fedora ==
* A new feature that allows users to create pools that encrypt all data
devices and consequently securely store all user data.

== Scope ==
* Proposal owners:
** Package Rust crate 

[Bug 1858952] New: perl-IO-Compress-2.095 is available

[bugzilla]

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

Bug ID: 1858952
   Summary: perl-IO-Compress-2.095 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-IO-Compress
  Keywords: FutureFeature, Triaged
  Assignee: jples...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: jples...@redhat.com, mmasl...@redhat.com,
p...@city-fan.org, perl-devel@lists.fedoraproject.org,
rland...@redhat.com
  Target Milestone: ---
Classification: Fedora



Latest upstream release: 2.095
Current version/release in rawhide: 2.093-2.fc32
URL: http://search.cpan.org/dist/IO-Compress/

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


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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

[Bug 1858951] New: perl-ExtUtils-HasCompiler-0.022 is available

[bugzilla]

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

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



Latest upstream release: 0.022
Current version/release in rawhide: 0.021-9.fc32
URL: http://search.cpan.org/dist/ExtUtils-HasCompiler/

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


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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

Re: Fedora 33 System-Wide Change proposal: CMake to do out-of-source builds

[Dominik 'Rathann' Mierzejewski]

On Monday, 20 July 2020 at 21:39, Neal Gompa wrote:
> On Mon, Jul 20, 2020 at 3:32 PM Dominik 'Rathann' Mierzejewski
>  wrote:
[...]
> > Sorry, but when you break other packagers workflows, the least you
> > can do is provide a clean solution to make them work again. Making a
> > change and telling affected people to "fix it themselves" is just
> > not excellent.
> >
> 
> There is a build for cmake3 with backported macros in testing:
> https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-a911888c3e
> 
> It just needs karma to make it to stable.

Alright, I'll try to test it this week and give karma.

[...]
> Well, right now I'm trying to figure out how to implement this for
> EPEL 8. The trouble is that EPEL 8 has CMake 3.11, which doesn't have
> everything I need to do this properly, so I'm trying to come up with
> something still.

That is much appreciated, thank you.

> As it is, for now, you can revert to the old behavior by putting in
> your spec
> 
> %global __cmake_in_source_build 1
> 
> and the %cmake macro will behave exactly like before, requiring manual
> effort to do an out of source build.

Alright, that helps. Thanks.

> Also note that this variable is set for EPEL and current supported
> Fedora releases. It is *unset* for Fedora 33+.

I see, thanks for spelling it out.

Regards,
Dominik
-- 
Fedora   https://getfedora.org  |  RPM Fusion  http://rpmfusion.org
There should be a science of discontent. People need hard times and
oppression to develop psychic muscles.
-- from "Collected Sayings of Muad'Dib" by the Princess Irulan
___
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

Re: cmake-3.18.0-2.fc33 (or 3.18.0-1.fc33.1) in rawhide is broken!

[Neal Gompa]

On Mon, Jul 20, 2020 at 3:44 PM Kaleb Keithley  wrote:
>
> On Mon, Jul 20, 2020 at 1:48 PM Neal Gompa  wrote:
>>
>>
>>
>> Your spec file is a complete mess, so I have not yet touched it to fix it.
>
>
> Not _my_ spec file. Is this another episode of whinging about %ifdef SUSE, 
> then I suggest you direct your comments at 
> https://github.com/ceph/ceph/blob/master/ceph.spec.in.  I'm sure they will 
> appreciate your usual candor.
>
> Because I'm sure what everyone wants is to maintain two files that are 99% 
> the same. Especially when there are conditionals.
>

Hardly. I maintain plenty of triple-distro (RH/Fedora, SUSE, and
Debian/Ubuntu) spec files of more complex software that are cleaner
than Ceph's.

The mess is because the Ceph spec file is tremendously regressive
compared to current standards for RH/Fedora and SUSE packaging. It
doesn't even have the minor fixes I made upstream to the spec for
libexecdir stuff.

>>
>> Here's an example of how I fixed one package:
>> https://src.fedoraproject.org/rpms/allegro5/c/2a59aa1daea345823b81c9b396f5766cba54da78
>
>
> That might actually be helpful.
>
> More constructive comments. Less snark.
>

I *was* going to fix it at some point, but having to parse a complex
spec file takes time and effort. And I *really* doubt anyone has
seriously analyzed that spec file in recent years.

Even *I* haven't completed my *own* analysis of it for rewriting it
for my personal use, since there's far too much cruft in the current
spec for me to be comfortable with me using for personal builds.




--
真実はいつも一つ！/ 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

[Bug 1858942] New: perl-Compress-Raw-Bzip2-2.095 is available

[bugzilla]

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

Bug ID: 1858942
   Summary: perl-Compress-Raw-Bzip2-2.095 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Compress-Raw-Bzip2
  Keywords: FutureFeature, Triaged
  Assignee: jples...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: jples...@redhat.com, ka...@ucw.cz, p...@city-fan.org,
perl-devel@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



Latest upstream release: 2.095
Current version/release in rawhide: 2.093-2.fc32
URL: http://search.cpan.org/dist/Compress-Raw-Bzip2/

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


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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

Re: Help me bring AVIF to Fedora

[Andy Mender]

On Sun, 19 Jul 2020 at 23:15, Robert-André Mauchin 
wrote:

> Hello,
>
> I'd like some help to review:
>  - libavif: https://bugzilla.redhat.com/show_bug.cgi?id=1858419
>
>  - qt-avif-image-plugin:
> https://bugzilla.redhat.com/show_bug.cgi?id=1858639
>
> I can swap with anything.
>
>
Took libavif. Will give it a spin tomorrow after work :).

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

Re: cmake-3.18.0-2.fc33 (or 3.18.0-1.fc33.1) in rawhide is broken!

[Kaleb Keithley]

On Mon, Jul 20, 2020 at 1:48 PM Neal Gompa  wrote:

>
>
> Your spec file is a complete mess, so I have not yet touched it to fix it.
>

Not _my_ spec file. Is this another episode of whinging about %ifdef SUSE,
then I suggest you direct your comments at
https://github.com/ceph/ceph/blob/master/ceph.spec.in.  I'm sure they will
appreciate your usual candor.

Because I'm sure what everyone wants is to maintain two files that are 99%
the same. Especially when there are conditionals.


> Here's an example of how I fixed one package:
>
> https://src.fedoraproject.org/rpms/allegro5/c/2a59aa1daea345823b81c9b396f5766cba54da78


That might actually be helpful.

More constructive comments. Less snark.

--

Kaleb
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Fedora 33 System-Wide Change proposal: CMake to do out-of-source builds

[Neal Gompa]

On Mon, Jul 20, 2020 at 3:32 PM Dominik 'Rathann' Mierzejewski
 wrote:
>
> On Wednesday, 08 July 2020 at 15:19, Igor Raits wrote:
> > On Wed, 2020-07-08 at 14:13 +0200, Vitaly Zaitsev via devel wrote:
> > > On 07.07.2020 19:57, Orion Poplawski wrote:
> > > > What's the plan for EPEL8/7 compatibility?
> > >
> > > +1. The new Cmake macros behaviour must be backported to EPEL7/8.
> >
> > Feel free to submit patches to cmake3 and epel-rpm-macros.
>
> Sorry, but when you break other packagers workflows, the least you can
> do is provide a clean solution to make them work again. Making a change
> and telling affected people to "fix it themselves" is just not
> excellent.
>

There is a build for cmake3 with backported macros in testing:
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-a911888c3e

It just needs karma to make it to stable.

> > > Currently all fixed by proven packages SPEC files cannot be built on
> > > EPEL branches.
>
> A better way would have been to introduce a new macro and migrate all
> packages to it gradually. Then, after giving a sufficient grace period,
> at some point you could make the old macro error out pointing to
> current documentation.
>
> Currently, I have top adapt all my cmake-using specs that were doing
> out-of-tree builds across Fedora and EPEL using the %cmake3 macro.
>
> This doesn't work anymore:
>
> mkdir -p build
> cd build
> %cmake3 \
> ..
> %make_build
>
> And that makes me grumpy unless you can provide a clean way to make
> this work again across Fedora and EPEL without any %ifdefs.
>

Well, right now I'm trying to figure out how to implement this for
EPEL 8. The trouble is that EPEL 8 has CMake 3.11, which doesn't have
everything I need to do this properly, so I'm trying to come up with
something still.

As it is, for now, you can revert to the old behavior by putting in your spec

%global __cmake_in_source_build 1

and the %cmake macro will behave exactly like before, requiring manual
effort to do an out of source build.

Also note that this variable is set for EPEL and current supported
Fedora releases. It is *unset* for Fedora 33+.



--
真実はいつも一つ！/ 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

Re: cmake-3.18.0-2.fc33 (or 3.18.0-1.fc33.1) in rawhide is broken!

[Dominik 'Rathann' Mierzejewski]

On Monday, 20 July 2020 at 19:37, Neal Gompa wrote:
> On Mon, Jul 20, 2020 at 1:29 PM Kaleb Keithley  wrote:
> >
> >
> > On 2020-07-17 I built ceph-15.2.4-5 (and ceph-15.2.4-6 --target=f33-java11) 
> > with cmake-3.18.0-1.fc33 and the build(s) were successful.
> >
> > Today, with cmake-3.18.0-2.fc33 (which I guess is a respin of cmake-
> > 3.18.0-1.fc33.1, a.k.a. 3.18.0-1.1) my scratch builds are failing with:
> >
> >   ...
> >
> >   + make -j5
> >   make: *** No targets specified and no makefile found.  Stop.
> >
> > see, e.g., https://koji.fedoraproject.org/koji/watchlogs?taskID=47508501
> >
> > No changes to the .spec other than Release and %changelog.
> >
> > Anyone else seeing this?
> >
> 
> This is because ceph is not adapted yet for
> https://fedoraproject.org/wiki/Changes/CMake_to_do_out-of-source_builds
> 
> Your spec file is a complete mess, so I have not yet touched it to fix it.
> 
> Here's an example of how I fixed one package:
> https://src.fedoraproject.org/rpms/allegro5/c/2a59aa1daea345823b81c9b396f5766cba54da78

This doesn't help to fix this:

%build
mkdir -p build
cd build
%cmake3 \
..
%make_build

Help?

Regards,
Dominik
-- 
Fedora   https://getfedora.org  |  RPM Fusion  http://rpmfusion.org
There should be a science of discontent. People need hard times and
oppression to develop psychic muscles.
-- from "Collected Sayings of Muad'Dib" by the Princess Irulan
___
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

Re: Fedora 33 System-Wide Change proposal: CMake to do out-of-source builds

[Dominik 'Rathann' Mierzejewski]

On Wednesday, 08 July 2020 at 15:19, Igor Raits wrote:
> On Wed, 2020-07-08 at 14:13 +0200, Vitaly Zaitsev via devel wrote:
> > On 07.07.2020 19:57, Orion Poplawski wrote:
> > > What's the plan for EPEL8/7 compatibility?
> > 
> > +1. The new Cmake macros behaviour must be backported to EPEL7/8.
> 
> Feel free to submit patches to cmake3 and epel-rpm-macros.

Sorry, but when you break other packagers workflows, the least you can
do is provide a clean solution to make them work again. Making a change
and telling affected people to "fix it themselves" is just not
excellent.

> > Currently all fixed by proven packages SPEC files cannot be built on
> > EPEL branches.

A better way would have been to introduce a new macro and migrate all
packages to it gradually. Then, after giving a sufficient grace period,
at some point you could make the old macro error out pointing to
current documentation.

Currently, I have top adapt all my cmake-using specs that were doing
out-of-tree builds across Fedora and EPEL using the %cmake3 macro.

This doesn't work anymore:

mkdir -p build
cd build
%cmake3 \
..
%make_build

And that makes me grumpy unless you can provide a clean way to make
this work again across Fedora and EPEL without any %ifdefs.

Regards,
Dominik
-- 
Fedora   https://getfedora.org  |  RPM Fusion  http://rpmfusion.org
There should be a science of discontent. People need hard times and
oppression to develop psychic muscles.
-- from "Collected Sayings of Muad'Dib" by the Princess Irulan
___
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

Re: cmake-3.18.0-2.fc33 (or 3.18.0-1.fc33.1) in rawhide is broken!

[Dominik 'Rathann' Mierzejewski]

On Monday, 20 July 2020 at 20:46, Kamil Dudka wrote:
> On Monday, July 20, 2020 8:35:37 PM CEST Neal Gompa wrote:
> > Or you could just use "%global __cmake_in_source_build 1" which
> > reverts to the previous behavior.
> 
> That does not make any sense.  The packages I talk about have used
> out of source builds since forever.
> 
> > Or you could *actually* make it do it out of source even with older
> > Fedora releases as I did with my example commit.
> 
> I thought I did.  And not only for Fedora releases ;-)
> 
> https://copr.fedorainfracloud.org/coprs/kdudka/predator/build/1565751/

Is there any way to make this portable across all Fedora releases and
EPEL? I'd like to avoid %ifdeffery if possible.

Regards,
Dominik
-- 
Fedora   https://getfedora.org  |  RPM Fusion  http://rpmfusion.org
There should be a science of discontent. People need hard times and
oppression to develop psychic muscles.
-- from "Collected Sayings of Muad'Dib" by the Princess Irulan
___
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

Re: How do Fedora developers get access to devtoolset for testing.

[Jonathan Wakely]

On 20/07/20 13:09 -0500, Steven Munroe wrote:

Then I would have to learn what a "EL7 mock chroot" is. And how it is


man mock


different from "rpmbuild "


That builds the package on your local system, using the packages
available on your local system. If that's Fedora, then you're not
going to be able to install devtoolset.


and "fedpkg  --release f33 scratch-build".


That submits a build to koji, to build it using the packages available
in the f33 buildroot. That's Fedora, so again, you're not going to be
able to make use of devtoolset (because it's not in the f33
buildroot).


The documentation is a bit sparse ...


I think you need to take a step back and figure out what you're doing.

Why are you asking fedpkg to build for f33 if you are trying to
package something for el7 and el8?

If you want to package something for el7 and/or el8, using the
packages present on el7 or el8, stop trying to build on Fedora.
They're not the same.

There are several ways to build for el7 or el8:

1) Install CentOS 7 (or 8) and then build locally. This can be on a
physical machine or VM.  But it's quite a heavyweight approach. There
are much simpler ways.

2) Build in a container using a CentOS 7 (or 8) image, using podman or
docker. That's less heavyweight than setting up a whole new machine,
but there are still easier ways.

3) Use mock to build locally in a chroot that contains the filesystem
and the packages from CentOS 7 (or 8). You can use the 'fedpkg
mockbuild' command to simplify that.

4) Use koji to build the package using the repos for CentOS 7 (or 8).
That's what 'fedpkg scratch-build' and 'fedpkg build' do, but you need
to tell koji which distro to use with --release epel7, not f33.

What you're trying to do now sems to be to create a frankenstein
system containing bits of fedora and bits of el7, then build on that
system.  That's a terrible idea. Even if you manage to bring the
monster to life, it will be a freak, and nobody else trying to build
your package will be using the same environment.

___
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

Re: cmake-3.18.0-2.fc33 (or 3.18.0-1.fc33.1) in rawhide is broken!

[Kamil Dudka]

On Monday, July 20, 2020 8:35:37 PM CEST Neal Gompa wrote:
> Or you could just use "%global __cmake_in_source_build 1" which
> reverts to the previous behavior.

That does not make any sense.  The packages I talk about have used
out of source builds since forever.

> Or you could *actually* make it do it out of source even with older
> Fedora releases as I did with my example commit.

I thought I did.  And not only for Fedora releases ;-)

https://copr.fedorainfracloud.org/coprs/kdudka/predator/build/1565751/

Kamil

___
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

Re: cmake-3.18.0-2.fc33 (or 3.18.0-1.fc33.1) in rawhide is broken!

[Neal Gompa]

On Mon, Jul 20, 2020 at 2:31 PM Kamil Dudka  wrote:
>
> On Monday, July 20, 2020 7:37:25 PM CEST Neal Gompa wrote:
> > This is because ceph is not adapted yet for
> > https://fedoraproject.org/wiki/Changes/CMake_to_do_out-of-source_builds
>
> Yes, this change broke a lot of builds as it had been discussed on this list.
>
> > Your spec file is a complete mess, so I have not yet touched it to fix it.
>
> The spec file looks fine to me.  Have you ever seen texlive.spec?
>

Yes, I have. It's *evil*. It also doesn't use CMake. It's irrelevant
in the context of this change.

> > Here's an example of how I fixed one package:
> > https://src.fedoraproject.org/rpms/allegro5/c/2a59aa1daea345823b81c9b396f576
> > 6cba54da78
>
> I had exactly the same problem in my own projects.  Appending -B. at the end
> of the line(s) starting with %cmake has fixed it:
>
> https://github.com/kdudka/predator/commit/34ef2198
>

Or you could just use "%global __cmake_in_source_build 1" which
reverts to the previous behavior.

Or you could *actually* make it do it out of source even with older
Fedora releases as I did with my example commit.


-- 
真実はいつも一つ！/ 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

Re: cmake-3.18.0-2.fc33 (or 3.18.0-1.fc33.1) in rawhide is broken!

[Kamil Dudka]

On Monday, July 20, 2020 7:37:25 PM CEST Neal Gompa wrote:
> This is because ceph is not adapted yet for
> https://fedoraproject.org/wiki/Changes/CMake_to_do_out-of-source_builds

Yes, this change broke a lot of builds as it had been discussed on this list.

> Your spec file is a complete mess, so I have not yet touched it to fix it.

The spec file looks fine to me.  Have you ever seen texlive.spec?

> Here's an example of how I fixed one package:
> https://src.fedoraproject.org/rpms/allegro5/c/2a59aa1daea345823b81c9b396f576
> 6cba54da78
 
I had exactly the same problem in my own projects.  Appending -B. at the end 
of the line(s) starting with %cmake has fixed it:

https://github.com/kdudka/predator/commit/34ef2198

Kamil

___
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

Re: How do Fedora developers get access to devtoolset for testing.

[Steven Munroe]

On 20/07/20 17:08 +0100, Jonathan Wakely wrote:
...
Why can't you install it in an On 20/07/20 17:08 +0100, Jonathan Wakely wrote:
...
Why can't you install it in an EL7 mock chroot, as suggested earlier?
There's nothing special about devtoolset here, EL7 packages just
aren't meant to work on F32.

Then I would have to learn what a "EL7 mock chroot" is. And how it is
different from "rpmbuild " and "fedpkg  --release f33
scratch-build". The documentation is a bit sparse ...
___
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

Re: Enable EarlyOOM on Fedora KDE - Fedora 33 Self-Contained Change proposal

[Simon Farnsworth]

> On 20 Jul 2020, at 15:40, Stephen John Smoogen  wrote:
> 
> On Mon, 20 Jul 2020 at 05:04, Kevin Kofler  > wrote:
>> 
>> John M. Harris Jr wrote:
>>> Userspace isn't dead when a system is thrashing. Your software is still
>>> running. If it gets killed, you're most likely going to lose your data.
>> 
>> The thing is, there are various levels of thrashing. In some cases, the
>> system is so busy that you have no chance to bring it back to responsiveness
>> for many minutes, up to hours. (Other than hitting the Reset or Power
>> button, of course.) I have had cases where not even sshd would respond. (The
>> fact that login has been blocking on D-Bus since the introduction of
>> systemd-logind does not help either. Login timeouts are something that was
>> just never happening in the past, now they are common under heavy load.)
>> 
>> That said, I do not see how the EarlyOOM heuristic, which allows, depending
>> on the exact settings, something like 80-90% of swap to be used IN ADDITION
>> to 90+% RAM (and will only start doing anything if BOTH RAM and swap are
>> full) can prevent thrashing in any reliable way. My thrashing scenarios have
>> had much less swap than that used. (I have twice as much swap than RAM, so
>> when the EarlyOOM heuristics trigger, my programs are already trying to use
>> almost 3 times as much RAM as is actually available!)
>> 
> 
> I think the problem is that you are using way too much swap for modern
> systems. The reasons for swap being 2x to 4x real memory was a 1980's
> solution when big RAM systems had 64 MB of ram but a server might need
> 128MB for certain tasks. This was 'reasonable' because the processors
> were slow but could still walk through 128 MB of space 'pretty' fast.
> As RAM got larger this 2x became 'cargo-culted' in various
> documentation and was still reasonable while processor speed went up.
> You could still have a system with 512MB of ram and walk through 1024
> to 2048 GB of swap in similar times as the 128 MB.

Also affected by the way some UNIXes handled commit and fork (the things Linux 
heuristic overcommit was designed to avoid needing excess swap for). In the 
best case, you needed as much swap as RAM, so that a full size process (64 MB 
in your 1980s system) could allocate an extra 64 MB to fork; in the worst case, 
things were using that swap and you needed some multiple just for commit 
accounting.

IIRC, there were also some systems where the available space for committing was 
set to the size of swap - hence the need for 2x RAM. One for matching your RAM 
and allowing you to use it, one for the space consumed during a fork.

Linux's use of overcommit means that this isn't an issue for Fedora, though.
-- 
Simon___
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

Re: cmake-3.18.0-2.fc33 (or 3.18.0-1.fc33.1) in rawhide is broken!

[Gwyn Ciesla via devel]

You can work around it for now with %global __cmake_in_source_build 1

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

Sent with ProtonMail Secure Email.

‐‐‐ Original Message ‐‐‐
On Monday, July 20, 2020 12:27 PM, Kaleb Keithley  wrote:

> On 2020-07-17 I built ceph-15.2.4-5 (and ceph-15.2.4-6 --target=f33-java11) 
> with cmake-3.18.0-1.fc33 and the build(s) were successful.
> 

> Today, with cmake-3.18.0-2.fc33 (which I guess is a respin of cmake-
> 3.18.0-1.fc33.1, a.k.a. 3.18.0-1.1) my scratch builds are failing with:
> 

>   ...
> 

>   + make -j5
>   make: *** No targets specified and no makefile found.  Stop.
> 

> see, e.g., https://koji.fedoraproject.org/koji/watchlogs?taskID=47508501
> 

> No changes to the .spec other than Release and %changelog.
> 

> Anyone else seeing this?
> 

> --
> 

> Kaleb

signature.asc
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: cmake-3.18.0-2.fc33 (or 3.18.0-1.fc33.1) in rawhide is broken!

[Neal Gompa]

On Mon, Jul 20, 2020 at 1:29 PM Kaleb Keithley  wrote:
>
>
> On 2020-07-17 I built ceph-15.2.4-5 (and ceph-15.2.4-6 --target=f33-java11) 
> with cmake-3.18.0-1.fc33 and the build(s) were successful.
>
> Today, with cmake-3.18.0-2.fc33 (which I guess is a respin of cmake-
> 3.18.0-1.fc33.1, a.k.a. 3.18.0-1.1) my scratch builds are failing with:
>
>   ...
>
>   + make -j5
>   make: *** No targets specified and no makefile found.  Stop.
>
> see, e.g., https://koji.fedoraproject.org/koji/watchlogs?taskID=47508501
>
> No changes to the .spec other than Release and %changelog.
>
> Anyone else seeing this?
>

This is because ceph is not adapted yet for
https://fedoraproject.org/wiki/Changes/CMake_to_do_out-of-source_builds

Your spec file is a complete mess, so I have not yet touched it to fix it.

Here's an example of how I fixed one package:
https://src.fedoraproject.org/rpms/allegro5/c/2a59aa1daea345823b81c9b396f5766cba54da78



-- 
真実はいつも一つ！/ 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

cmake-3.18.0-2.fc33 (or 3.18.0-1.fc33.1) in rawhide is broken!

[Kaleb Keithley]

On 2020-07-17 I built ceph-15.2.4-5 (and ceph-15.2.4-6 --target=f33-java11)
with cmake-3.18.0-1.fc33 and the build(s) were successful.

Today, with cmake-3.18.0-2.fc33 (which I guess is a respin of cmake-
3.18.0-1.fc33.1, a.k.a. 3.18.0-1.1) my scratch builds are failing with:

  ...

  + make -j5
  make: *** No targets specified and no makefile found.  Stop.

see, e.g., https://koji.fedoraproject.org/koji/watchlogs?taskID=47508501

No changes to the .spec other than Release and %changelog.

Anyone else seeing this?

--

Kaleb
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Remove all non UK/USA English spell checker variants from default Fedora installation

[Robbie Harwood]

Germano Massullo  writes:

> All desktop oriented Fedora installers install on the system packages:
> hunspell
> hunspell-en
> hunspell-en-GB
> hunspell-en-US
>
> When a user opens the language list of the spell checker, is has ~24
> different English options, like English (Antigua and Barbuda), English
> (Australia), English (Bahamas), English (Belize), etc. (See screenshot [1])
> People who are not native English speakers have this list even bigger
> because they will have their own language entry, plus others.
>
> Since the huge list is brought by hunspell-en, can we just ship Fedora
> with hunspell-en-GB and hunspell-en-US ?
> Another option could be to move all non GB/USA English variants to other
> hunspell-en-* packages as I said in ticket [2]

There's some disparity between your subject (stop shipping all non
US/UK) and the bug (separate packaging).  I care not for packaging, but
I care a lot about locales being present.  A personal anecdote:

I'm a native English speaker.  My partner is a native English speaker.
We can mostly use each other's computers - with the exception of
anything that uses spellcheck.  This is because we grew up needing
different locales, and (surprise) they're not on your list.  It's a
frustrating and surprisingly hostile experience for the computer to flag
random words that you typed with "WRONG" - words that you know you
spelled right and were completely sure were correct but now have to
question.

We have these different English variations for a reason.  By all means,
make the spellchecker default to your current locale.  But don't make
this harder for the rest of us.  Somewhere along the line we acquired
this idea that "eh, anyone can do work in en_US" and that's really not
true - but it is self-fulfilling.

I would love it if I could ssh to machines and have my preferred locale
present, but we don't seem to be in that future.  We localized,
performed all these translations, and it feels like we want to undo all
that work in the name of minimization.  While we're having other
discussions about inclusion, let's not forget the value in having the
computer speak your language.

Thanks,
--Robbie


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

[Bug 1856886] perl-HTTP-BrowserDetect-3.30 is available

[bugzilla]

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

Upstream Release Monitoring  
changed:

   What|Removed |Added

Summary|perl-HTTP-BrowserDetect-3.2 |perl-HTTP-BrowserDetect-3.3
   |9 is available  |0 is available



--- Comment #1 from Upstream Release Monitoring 
 ---
Latest upstream release: 3.30
Current version/release in rawhide: 3.27-1.fc33
URL: http://search.cpan.org/dist/HTTP-BrowserDetect/

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


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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

Re: Removing packages from module

[Aleksei Bavshin]

Petr and Daniel, thanks a lot for your replies.

I hope some of mentioned limitations could be reflected in the
modularity documentation. I read through most of it (including the
drafts for f33 change) and I don't feel that the consequences of adding
package to the module are clearly communicated.

And maybe something could be added to the modulemd spec to reflect that
the specific package is no longer required starting from release x. I
don't expect that to work from updates-modular for branched releases,
but having the ability to drop packages from module on a development
release would be awesome.

On 7/20/20 4:46 AM, Petr Pisar wrote:
> On Fri, Jul 17, 2020 at 02:14:49PM -0700, Aleksei Bavshin wrote:
>> The real question is how to do the change in f33 considering that f32
>> and f33 modules must be built from the same modulemd file.
> 
> You wrap a %files section of the package you want to remove with a condition
> based on the Fedora version:
> 
> %if %{fedora} < 33
> %files
> ...
> %end
> 
> This will cause the when building the module component, rpmbuild won't produce
> the unwanted binary package on F33, but it will produce it on F32.
> 
> The only problem is if that is the only binary package produced by the spec
> file. Then rpmbuild would report an error, because it would consider it
> a packaging mistake. But it can be worked around by produced a dummy package
> instead:
> 
> %if %{fedora} < 33
> %files
> ...
> %else
> %files -n dummy
> %end
> 
> and filtering out the dummy package from the module on modulemd level with
> /data/filetr/rpms/dummy entry.>
>> And now I'm curious what would happen if I specify `platform: [-f33]`
>> and publish new module build. Would that remove previously published
>> metadata from rawhide?
> 
> No. Rawhide repository is composed from the latest builds tagged into
> a rawhide tag. That means Rawhide would still contain the last module built
> from f33 platform.
> 
>> I guess the right answer is somewhere around servicelevels and `eol`
>> specification.
>>
> Theoretically yes. You can file a releng request
>  of moduel_eol type to shorten the EOL.
> But I worry that a compose process does not respect the EOL dates and instead
> the EOLed modules are removed from a compose configuration by relengs
> manually once before branching a new Fedora release (33 is the next one).
> 
> -- Petr
-- 
With best regards,
Aleksei Bavshin



signature.asc
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: How do Fedora developers get access to devtoolset for testing.

[Jonathan Wakely]

On 20/07/20 17:08 +0100, Jonathan Wakely wrote:

On 20/07/20 10:54 -0500, Steven Munroe wrote:

That looks like a more complete list. Still having problems with dependencies:

$ sudo dnf install devtoolset-9-gcc-9.3.1-2.el7.ppc64le.rpm
devtoolset-9-gcc-c++-9.3.1-2.el7.ppc64le.rpm
devtoolset-9-runtime-9.1-0.el7.ppc64le.rpm
devtoolset-9-libstdc++-devel-9.3.1-2.el7.ppc64le.rpm
Last metadata expiration check: 0:11:27 ago on Mon 20 Jul 2020 10:40:31 AM CDT.
Error:
Problem 1: conflicting requests
- nothing provides libmpfr.so.4()(64bit) needed by
devtoolset-9-gcc-9.3.1-2.el7.ppc64le
Problem 2: conflicting requests
- nothing provides libmpfr.so.4()(64bit) needed by
devtoolset-9-gcc-c++-9.3.1-2.el7.ppc64le

But:

$ sudo dnf install mpfr
Last metadata expiration check: 0:12:04 ago on Mon 20 Jul 2020 10:40:31 AM CDT.
Package mpfr-4.0.2-4.fc32.ppc64le is already installed.
Dependencies resolved.

So devtoolset must want a "special" mpfr but it is not obvious which
devtoolset package provides.


It's not special, it's just older.

The one in F32 provides libmpfr.so.6 IIRC, which is a different SONAME
to the one in EL7, so incompatible with the EL7 devtoolset.


Why can't you install it in an EL7 mock chroot, as suggested earlier?

There's nothing special about devtoolset here, EL7 packages just
aren't meant to work on F32.

___
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

Re: [Fedora-packaging] RPM-level auto release and changelog bumping - Fedora 33 System-Wide Change proposal

[Nicolas Mailhot via devel]

Le dimanche 19 juillet 2020 à 10:39 -0700, Kevin Fenzi a écrit :
> On Mon, Jul 13, 2020 at 10:17:11AM +0200, Nicolas Mailhot via devel
> wrote:
> > Tough it is a litteral key = value file with no fancy formatting
> > nor
> > even ini-like sections, and a handful of variables. Very boring
> > KISS
> > stuff.
> 
> Sure, but a file with 16 spaces and a newline is pretty confusing.

I will add a line of comment instead. The confusion is due to the fact
rpmbuild wants source files to exist before the build starts, and wants
them to be more than 13 bytes. I thought filling with spaces would
convey the empty file idea, I was wrong, adding a comment is trivial
and the parsing code is robust WRT comment lines, so no biggie to
change and improve.

Thank you for the enhancement suggestion!

> But then you know that exact thing was built. 
> With this setup you look at the git hash in koji and... it's the next
> commit after that thats exactly this build? Thats really messy.

The system separates build commits from modification commits.

It’s not like right now when most commits are modification *and* build
commits, except when they are not (because the change was done in
several commits, because the build failed but git still pretends it
occured, because a branch was EOLed before the modification process
finished, because the commit tracked a build that did not pass bodhi
gating, etc etc.)

The proposed system is a lot more clear and strict, for a build to be
tracked in git it needs to have actually succeeded and be commited
back, anything else is packager WIP. Making git history something you
can rely upon.

> Right, I was suggesting _changing_ your macros for this workflow. 
> 
> maintainer makes changes, runs scratch builds, tests, etc.
> They decide everything is good for an official build. 
> They generate the files and the macros just use those generated
> files,
> they don't bump anything or require a post build checkin.

You do not need to change the macros for this workflow, they already
support reproducible replay. Just prepare your build out of band and
then ask to build it in reproducible mode.

That only requires buildsys support to set the variable that activates
reproducible mode, and buildsys or packager support to make sure the
buildroot content matches the test builds (macros can do a lot of
things, they can not manage buildroot state in stead of the build
system).

However what this amounts to is the following:

1. build packages in scratch mode
2. check
3. commit
4. rebuild scratch builds in reproducible mode

That is more complex than the target workflow in the macros

1. build packages
2. check
3. decide to keep the packages, and commit back

The second workflow is more reliable than the first one, because the
second preserves the packages you tested, instead of hoping nothing
changed in the buildroot between the two build steps.

Of course doing it in 3 steps requires pairing back commit with bodhi
gating, absent bodhi changes it will probably be more involved at
first.

But the fact is it *can* evolve to a 3-step process with infra help,
and the evolution is consistent with what we’ve been trying to achieve
in the past years, and the current 4-step process is also supported at
macro level, as long as fedpkg/koji learns to set one variable (*not*
rocket science). And setting one variable is no different from the
generic bcond stuff ELN people want to happen.

Regards,

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

Re: How do Fedora developers get access to devtoolset for testing.

[Jonathan Wakely]

On 20/07/20 10:54 -0500, Steven Munroe wrote:

That looks like a more complete list. Still having problems with dependencies:

$ sudo dnf install devtoolset-9-gcc-9.3.1-2.el7.ppc64le.rpm
devtoolset-9-gcc-c++-9.3.1-2.el7.ppc64le.rpm
devtoolset-9-runtime-9.1-0.el7.ppc64le.rpm
devtoolset-9-libstdc++-devel-9.3.1-2.el7.ppc64le.rpm
Last metadata expiration check: 0:11:27 ago on Mon 20 Jul 2020 10:40:31 AM CDT.
Error:
Problem 1: conflicting requests
 - nothing provides libmpfr.so.4()(64bit) needed by
devtoolset-9-gcc-9.3.1-2.el7.ppc64le
Problem 2: conflicting requests
 - nothing provides libmpfr.so.4()(64bit) needed by
devtoolset-9-gcc-c++-9.3.1-2.el7.ppc64le

But:

$ sudo dnf install mpfr
Last metadata expiration check: 0:12:04 ago on Mon 20 Jul 2020 10:40:31 AM CDT.
Package mpfr-4.0.2-4.fc32.ppc64le is already installed.
Dependencies resolved.

So devtoolset must want a "special" mpfr but it is not obvious which
devtoolset package provides.


It's not special, it's just older.

The one in F32 provides libmpfr.so.6 IIRC, which is a different SONAME
to the one in EL7, so incompatible with the EL7 devtoolset.

___
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

Re: How do Fedora developers get access to devtoolset for testing.

[Steven Munroe]

That looks like a more complete list. Still having problems with dependencies:

$ sudo dnf install devtoolset-9-gcc-9.3.1-2.el7.ppc64le.rpm
devtoolset-9-gcc-c++-9.3.1-2.el7.ppc64le.rpm
devtoolset-9-runtime-9.1-0.el7.ppc64le.rpm
devtoolset-9-libstdc++-devel-9.3.1-2.el7.ppc64le.rpm
Last metadata expiration check: 0:11:27 ago on Mon 20 Jul 2020 10:40:31 AM CDT.
Error:
 Problem 1: conflicting requests
  - nothing provides libmpfr.so.4()(64bit) needed by
devtoolset-9-gcc-9.3.1-2.el7.ppc64le
 Problem 2: conflicting requests
  - nothing provides libmpfr.so.4()(64bit) needed by
devtoolset-9-gcc-c++-9.3.1-2.el7.ppc64le

But:

$ sudo dnf install mpfr
Last metadata expiration check: 0:12:04 ago on Mon 20 Jul 2020 10:40:31 AM CDT.
Package mpfr-4.0.2-4.fc32.ppc64le is already installed.
Dependencies resolved.

So devtoolset must want a "special" mpfr but it is not obvious which
devtoolset package provides.
___
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

[Bug 1858528] perl-File-Path-2.17 is available

[bugzilla]

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



--- Comment #2 from Fedora Update System  ---
FEDORA-2020-2846760782 has been submitted as an update to Fedora 32.
https://bodhi.fedoraproject.org/updates/FEDORA-2020-2846760782


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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

[Bug 1858528] perl-File-Path-2.17 is available

[bugzilla]

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



--- Comment #3 from Fedora Update System  ---
FEDORA-2020-1845580db2 has been submitted as an update to Fedora 31.
https://bodhi.fedoraproject.org/updates/FEDORA-2020-1845580db2


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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

[Bug 1858528] perl-File-Path-2.17 is available

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED
   Fixed In Version||perl-File-Path-2.17-1.fc33



--- Comment #1 from Petr Pisar  ---
A bug-fix release suitable for all Fedoras.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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

[Bug 1858481] perl-Module-CoreList-5.20200717 is available

[bugzilla]

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



--- Comment #3 from Fedora Update System  ---
FEDORA-2020-c802fdad2e has been submitted as an update to Fedora 31.
https://bodhi.fedoraproject.org/updates/FEDORA-2020-c802fdad2e


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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

[Bug 1858481] perl-Module-CoreList-5.20200717 is available

[bugzilla]

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



--- Comment #2 from Fedora Update System  ---
FEDORA-2020-20b70fc964 has been submitted as an update to Fedora 32.
https://bodhi.fedoraproject.org/updates/FEDORA-2020-20b70fc964


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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

[Bug 1858528] perl-File-Path-2.17 is available

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
 CC|ppi...@redhat.com   |
   Doc Type|--- |If docs needed, set a value




-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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

Re: Enable EarlyOOM on Fedora KDE - Fedora 33 Self-Contained Change proposal

[Stephen John Smoogen]

On Mon, 20 Jul 2020 at 05:04, Kevin Kofler  wrote:
>
> John M. Harris Jr wrote:
> > Userspace isn't dead when a system is thrashing. Your software is still
> > running. If it gets killed, you're most likely going to lose your data.
>
> The thing is, there are various levels of thrashing. In some cases, the
> system is so busy that you have no chance to bring it back to responsiveness
> for many minutes, up to hours. (Other than hitting the Reset or Power
> button, of course.) I have had cases where not even sshd would respond. (The
> fact that login has been blocking on D-Bus since the introduction of
> systemd-logind does not help either. Login timeouts are something that was
> just never happening in the past, now they are common under heavy load.)
>
> That said, I do not see how the EarlyOOM heuristic, which allows, depending
> on the exact settings, something like 80-90% of swap to be used IN ADDITION
> to 90+% RAM (and will only start doing anything if BOTH RAM and swap are
> full) can prevent thrashing in any reliable way. My thrashing scenarios have
> had much less swap than that used. (I have twice as much swap than RAM, so
> when the EarlyOOM heuristics trigger, my programs are already trying to use
> almost 3 times as much RAM as is actually available!)
>

I think the problem is that you are using way too much swap for modern
systems. The reasons for swap being 2x to 4x real memory was a 1980's
solution when big RAM systems had 64 MB of ram but a server might need
128MB for certain tasks. This was 'reasonable' because the processors
were slow but could still walk through 128 MB of space 'pretty' fast.
As RAM got larger this 2x became 'cargo-culted' in various
documentation and was still reasonable while processor speed went up.
You could still have a system with 512MB of ram and walk through 1024
to 2048 GB of swap in similar times as the 128 MB.

As processor speeds increased while disk speeds did not, there was a
tipping point where going into larger swap would be catastrophic. By
the early 2000's systems with 4x swap would go catatonic in thrashing
by the time you got even 1/2 of it full. Things seemed to have gotten
worse with multicore processors and threaded programs. This means that
larger numbers of tools are all trying to get access to 'live' RAM all
the time and if you go off to disks, you are sunk. These days, I think
that if you are needing more than 0.5 RAM in swap.. you are probably
going to go into thrashing hell pretty regularly... the speed
difference between memory and disks is too large and there are too
many processes all wanting some CPU time all the time.



-- 
Stephen J Smoogen.
___
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

[Bug 1858476] perl-CPAN-Perl-Releases-5.20200717 is available

[bugzilla]

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



--- Comment #3 from Fedora Update System  ---
FEDORA-2020-85392ab421 has been submitted as an update to Fedora 31.
https://bodhi.fedoraproject.org/updates/FEDORA-2020-85392ab421


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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

Re: Enable EarlyOOM on Fedora KDE - Fedora 33 Self-Contained Change proposal

[Michael Catanzaro]

On Mon, Jul 20, 2020 at 10:55 am, Kevin Kofler  
wrote:
That said, I do not see how the EarlyOOM heuristic, which allows, 
depending
on the exact settings, something like 80-90% of swap to be used IN 
ADDITION
to 90+% RAM (and will only start doing anything if BOTH RAM and swap 
are

full) can prevent thrashing in any reliable way.


Well you're right: on its own, earlyoom is unlikely to save you from 
thrashing if you have swap on disk. This is really designed to work 
well in combination with zram, and best with Benjamin's resource 
protection work as well. So please consider it alongside the other work.


Michael

___
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

[Bug 1858481] perl-Module-CoreList-5.20200717 is available

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

 Status|NEW |MODIFIED
 CC|jples...@redhat.com,|
   |ppi...@redhat.com   |
   Fixed In Version||perl-Module-CoreList-5.2020
   ||0717-1.fc33
   Doc Type|--- |If docs needed, set a value



--- Comment #1 from Petr Pisar  ---
An enhancement release suitable for all Fedoras.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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

[Bug 1858476] perl-CPAN-Perl-Releases-5.20200717 is available

[bugzilla]

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



--- Comment #2 from Fedora Update System  ---
FEDORA-2020-6327f493e8 has been submitted as an update to Fedora 32.
https://bodhi.fedoraproject.org/updates/FEDORA-2020-6327f493e8


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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

[Bug 1858476] perl-CPAN-Perl-Releases-5.20200717 is available

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED
   Fixed In Version||perl-CPAN-Perl-Releases-5.2
   ||0200717-1.fc33



--- Comment #1 from Petr Pisar  ---
An enhancement release suitable for all Fedoras.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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

[Bug 1858467] perl-Compress-Bzip2-2.28 is available

[bugzilla]

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



--- Comment #2 from Fedora Update System  ---
FEDORA-2020-ccb3c84ade has been submitted as an update to Fedora 32.
https://bodhi.fedoraproject.org/updates/FEDORA-2020-ccb3c84ade


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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

[Bug 1858476] perl-CPAN-Perl-Releases-5.20200717 is available

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

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




-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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

[Bug 1858467] perl-Compress-Bzip2-2.28 is available

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED
   Fixed In Version||perl-Compress-Bzip2-2.28-1.
   ||fc33



--- Comment #1 from Petr Pisar  ---
A bug-fix release suitable for all Fedoras.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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

[Bug 1858467] perl-Compress-Bzip2-2.28 is available

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
 CC|ppi...@redhat.com   |
   Doc Type|--- |If docs needed, set a value




-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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

Re: Orphaned packages looking for new maintainers

[Miro Hrončok]

On 20. 07. 20 15:28, Gwyn Ciesla via devel wrote:

python3-mypy maintainer here, I took it.


Thank you, Gwyn.

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

Re: Serial port sniffing?

[Steven A. Falco]

On 7/19/20 5:23 PM, Richard Shaw wrote:

I would like to monitor serial port communications read only, but I haven't 
found a tool that makes that easy in the Fedora repos.


I've done that with "socat" to monitor communications with an APC UPS.  Here is 
my recipe:

socat /dev/ttyU3412A,raw,echo=0 \
SYSTEM:'tee in.txt |socat - "PTY,link=/tmp/ttyV0,raw,echo=0,waitslave" |tee 
out.txt'

In the above, ttyU3412A is the physical serial port.  ttyV0 is created by 
socat, and that is what you connect to.  All traffic gets logged to the two 
.txt files.

Please note that this is one long command line.  The SYSTEM thing is an 
argument to the first socat.

Steve
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Orphaned packages looking for new maintainers

[Gwyn Ciesla via devel]

‐‐‐ Original Message ‐‐‐
On Monday, July 20, 2020 3:56 AM, Miro Hrončok  wrote:

> On 20. 07. 20 10:35, Miro Hrončok wrote:
> 

> > The following packages are orphaned and will be retired...
> > Depending on: python-typeshed (6), status change: 2020-07-13 (0 weeks ago)
> > python3-mypy (maintained by: dshea, limb)
> > python3-mypy-0.782-1.fc33.noarch requires python-typeshed = 
> > 0.1-0.20191009git.fc32
> > python3-mypy-0.782-1.fc33.src requires python-typeshed = 
> > 0.1-0.20191009git.fc32
> > home-assistant-cli (maintained by: fab)
> > home-assistant-cli-0.9.1-3.fc33.src requires python3-mypy = 0.782-1.fc33
> > python-pydantic (maintained by: jussilehtola)
> > python-pydantic-1.3-5.fc33.src requires python3-mypy = 0.782-1.fc33
> > python-pydocstyle (maintained by: tadej)
> > python-pydocstyle-5.0.2-2.fc33.src requires python3dist(mypy) = 0.782
> > python-rsa (maintained by: fale, jmontleon)
> > python-rsa-4.6-1.fc33.src requires python3-mypy = 0.782-1.fc33
> > thonny (maintained by: aivarannamaa, churchyard)
> > thonny-3.2.7-4.fc33.noarch requires python3-mypy = 0.782-1.fc33, 
> > python3.9dist(mypy) = 0.782
> 

> I could take python-typeshed if absolutely necessary, but I think the
> python3-mypy maintainers are better equipped to take care of it. Let me know.
> 


python3-mypy maintainer here, I took it.

> --
> 

> 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



signature.asc
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

[Bug 1858788] ddclient dependency missing

[bugzilla]

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

Scott Talbert  changed:

   What|Removed |Added

 CC||fedora...@rule.lv,
   ||perl-devel@lists.fedoraproj
   ||ect.org
  Component|ddclient|perl-Data-Validate-IP



--- Comment #4 from Scott Talbert  ---
OK, I see the problem.  perl-Data-Validate-IP is missing from playground.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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

Orphaned packages looking for new maintainers

[Miro Hrončok]

The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life

Note: If you received this mail directly you (co)maintain one of the affected
packages or a package that depends on one. Please adopt the affected package or
retire your depending package to avoid broken dependencies, otherwise your
package will be retired when the affected package gets retired.

Request package ownership via the *Take* button in he left column on
https://src.fedoraproject.org/rpms/

Full report available at:
https://churchyard.fedorapeople.org/orphans-2020-07-20.txt
grep it for your FAS username and follow the dependency chain.

Package  (co)maintainers   Status Change

Java-WebSocketorphan   2 weeks ago
amftools  churchyard, orphan   0 weeks ago
anchorman orphan   2 weeks ago
atoum orphan   4 weeks ago
beaconorphan   2 weeks ago
carto nodejs-sig, orphan   1 weeks ago
cinnamon-themes   jcpunk, orphan, suve 2 weeks ago
closure-compiler  orphan   0 weeks ago
datanucleus-maven-parent  orphan   5 weeks ago
docker-client-javajjohnstn, orphan, rgrunber   2 weeks ago
ebay-cors-filter  orphan   5 weeks ago
eclipse-remoteeclipse-sig, orphan  0 weeks ago
emacs-lua orphan   0 weeks ago
ember-media   mpreisle, orphan 2 weeks ago
felix-osgi-obrjcapik, mizdebsk, orphan 3 weeks ago
felix-shell   mizdebsk, orphan 3 weeks ago
foo2zjs   orphan   2 weeks ago
gabedit   itamarjp, orphan, rathann,   1 weeks ago
  scitech_sig
gallery3-openid   orphan   2 weeks ago
gdb-heap  orphan, siddhesh 2 weeks ago
gfal2-utilandreamanzi, gbitzes, orphan 0 weeks ago
gimp-normalmaporphan   1 weeks ago
gloobus-preview   orphan   2 weeks ago
glpi  orphan   3 weeks ago
gnome-mud orphan   2 weeks ago
gnusim8085orphan   1 weeks ago
gobby05   kevin, orphan5 weeks ago
golang-github-calmh-dugo-sig, orphan   1 weeks ago
golang-github-calmh-xdr   go-sig, orphan   1 weeks ago
golang-github-chmduquesne-go-sig, orphan   1 weeks ago
rollinghash
golang-github-d4l3k-messagediff   go-sig, orphan   1 weeks ago
golang-github-jackpal-gateway go-sig, orphan   1 weeks ago
golang-github-syncthing-notifygo-sig, orphan   1 weeks ago
golang-github-thejerf-suture  go-sig, orphan   1 weeks ago
golang-github-vitrun-qart go-sig, orphan   1 weeks ago
gr-iioorphan   2 weeks ago
grig  orphan   2 weeks ago
gspiceui  orphan   2 weeks ago
gtkmathview   orphan   2 weeks ago
hip   orphan   0 weeks ago
icon-slicer   alexl, caillon, caolanm, 4 weeks ago
  gnome-sig, johnp, mbarnes,
  orphan, rhughes, rstrode, ssp
iipsrvorphan   3 weeks ago
inception orphan   2 weeks ago
iptux orphan   2 weeks ago
jake  nodejs-sig, orphan, piotrp   1 weeks ago
javolutionorphan   5 weeks ago
joda-convert  mizdebsk, orphan, spike  3 weeks ago
js-jquery-datetimepicker  orphan   5 weeks ago
kosmtik

Fedora rawhide compose report: 20200720.n.0 changes

[Fedora Rawhide Report]

OLD: Fedora-Rawhide-20200719.n.0
NEW: Fedora-Rawhide-20200720.n.0

= SUMMARY =
Added images:1
Dropped images:  5
Added packages:  0
Dropped packages:3
Upgraded packages:   36
Downgraded packages: 0

Size of added packages:  0 B
Size of dropped packages:276.87 KiB
Size of upgraded packages:   2.47 GiB
Size of downgraded packages: 0 B

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

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

= DROPPED IMAGES =
Image: Silverblue dvd-ostree x86_64
Path: 
Silverblue/x86_64/iso/Fedora-Silverblue-ostree-x86_64-Rawhide-20200719.n.0.iso
Image: Cloud_Base vmdk ppc64le
Path: Cloud/ppc64le/images/Fedora-Cloud-Base-Rawhide-20200719.n.0.ppc64le.vmdk
Image: Cloud_Base raw-xz ppc64le
Path: Cloud/ppc64le/images/Fedora-Cloud-Base-Rawhide-20200719.n.0.ppc64le.raw.xz
Image: Container_Minimal_Base docker ppc64le
Path: 
Container/ppc64le/images/Fedora-Container-Minimal-Base-Rawhide-20200719.n.0.ppc64le.tar.xz
Image: Cloud_Base qcow2 ppc64le
Path: Cloud/ppc64le/images/Fedora-Cloud-Base-Rawhide-20200719.n.0.ppc64le.qcow2

= ADDED PACKAGES =

= DROPPED PACKAGES =
Package: amqp-1:1.0-12.20150701svn1688630.fc32
Summary: The AMQP specification
RPMs:amqp amqp-devel
Size:53.18 KiB

Package: csvdiff-0.3.1-12.fc33
Summary: Generate a diff between two CSV files on the command-line
RPMs:csvdiff
Size:28.65 KiB

Package: jp2a-1.0.7-6.fc32
Summary: Small utility that converts JPG images to ASCII (text) using libjpeg
RPMs:jp2a
Size:195.03 KiB


= UPGRADED PACKAGES =
Package:  Carla-1:2.2.0-0.1.rc1.fc33
Old package:  Carla-1:2.2-1.beta1.fc33
Summary:  Audio plugin host
RPMs: Carla Carla-devel Carla-vst lv2-carla
Size: 53.05 MiB
Size change:  1.82 MiB
Changelog:
  * Sun Jul 19 2020 Martin Gansser  - 
1:2.2.0-0.1.rc1
  - Update to 2.2.0-0.1.rc1


Package:  cmake-3.18.0-2.fc33
Old package:  cmake-3.18.0-1.fc33
Summary:  Cross-platform make system
RPMs: cmake cmake-data cmake-doc cmake-filesystem cmake-gui 
cmake-rpm-macros
Size: 56.25 MiB
Size change:  1.05 KiB
Changelog:
  * Sat Jul 18 2020 Igor Raits  - 3.18.0-1.1
  - Enable out-of-source builds by default

  * Sun Jul 19 2020 Neal Gompa  - 3.18.0-2
  - Make in-source builds behave like before


Package:  ditaa-0.10-11.fc33
Old package:  ditaa-0.10-9.fc33
Summary:  Diagrams Through ASCII Art
RPMs: ditaa
Size: 88.10 KiB
Size change:  -3.01 KiB
Changelog:
  * Fri Jul 10 2020 Jiri Vanek  - 0.10-10
  - Rebuilt for JDK-11, see https://fedoraproject.org/wiki/Changes/Java11

  * Sun Jul 19 2020 Terje Rosten  - 0.10-11
  - Add patch from Debian to build with JDK 10+


Package:  dummy-test-package-crested-0-842.fc33
Old package:  dummy-test-package-crested-0-835.fc33
Summary:  Dummy Test Package called Crested
RPMs: dummy-test-package-crested
Size: 59.23 KiB
Size change:  456 B
Changelog:
  * Sun Jul 19 2020 packagerbot  - 0-836
  - rebuilt

  * Sun Jul 19 2020 packagerbot  - 0-837
  - rebuilt

  * Sun Jul 19 2020 packagerbot  - 0-838
  - rebuilt

  * Sun Jul 19 2020 packagerbot  - 0-839
  - rebuilt

  * Sun Jul 19 2020 packagerbot  - 0-840
  - rebuilt

  * Sun Jul 19 2020 packagerbot  - 0-841
  - rebuilt

  * Mon Jul 20 2020 packagerbot  - 0-842
  - rebuilt


Package:  dummy-test-package-gloster-0-933.fc33
Old package:  dummy-test-package-gloster-0-927.fc33
Summary:  Dummy Test Package called Gloster
RPMs: dummy-test-package-gloster
Size: 64.52 KiB
Size change:  359 B
Changelog:
  * Sun Jul 19 2020 packagerbot  - 0-928
  - rebuilt

  * Sun Jul 19 2020 packagerbot  - 0-929
  - rebuilt

  * Sun Jul 19 2020 packagerbot  - 0-930
  - rebuilt

  * Sun Jul 19 2020 packagerbot  - 0-931
  - rebuilt

  * Sun Jul 19 2020 packagerbot  - 0-932
  - rebuilt

  * Mon Jul 20 2020 packagerbot  - 0-933
  - rebuilt


Package:  fedora-obsolete-packages-33-17
Old package:  fedora-obsolete-packages-33-15
Summary:  A package to obsolete retired packages
RPMs: fedora-obsolete-packages
Size: 202.50 KiB
Size change:  469 B
Changelog:
  * Sun Jul 19 2020 Elliott Sales de Andrade  - 33-16
  - Bump Obsoletes for python2-beautifulsoup4

  * Sun Jul 19 2020 Miro Hron??ok  - 33-17
  - Obsolete python2-pillow-devel (#1858557)
  - Bump version of python2-pillow-tk and -qt


Package:  giac-1.6.0.7-1.fc33
Old package:  giac-1.5.0.85-3.fc33
Summary:  Computer Algebra System, Symbolic calculus, Geometry
RPMs: giac giac-devel giac-doc giac-xcas pgiac
Size: 75.91 MiB
Size change:  -1.65 MiB
Changelog:
  * Tue Jun 30 2020 Jeff Law  - 1.5.0.85-4
  - Fix broken configure test compromised by LTO

  * Sun Jul 19 2020 Antonio Trande  1.6.0.7-1
  - Update to 1.6.0 sub-7


Package:  git-2.28.0-0.1.rc1.fc33
Old package:  git

Re: Mass rebuild for f33-java11 side tag completed

[Fabio Valentini]

On Mon, Jul 20, 2020 at 2:24 PM Mat Booth  wrote:
>
> On Fri, 17 Jul 2020 at 09:34, Christian Heimes  wrote:
> >
> > > Hello!
> > >
> > > toatal packages: 610
> > > passed: 427
> > > failed: 176
> > >
> > > From the failures, there is 29 which passed in the copr before, and now 
> > > are thus failing
> > > from two
> > > reasons - unrelated change, or non-intel64-arch failure. I will put this 
> > > to FTBF bugs for
> > > those 29
> > > pacakges,
> > >
> > >
> > > In Monday, or as other duties allows I will fill FTBFS bugs for failures  
> > > with straces and
> > > reproduce
> > > steps.
> > > In default CC will be, me, Severin, decathrope and 
> > > java-devel(a)lists.fedoraproject.org.
> > >
> > > Note that during non-sidetag rebuild during fedora 33 branching in start 
> > > of August,  we
> > > can expect
> > > some indirect dependencies to fail.
> > >
> > > Thoughts?
> >
> > Hi Jiri,
> >
> > how will a merge of the Java 11 side tag into F33 Rawhide affect Dogtag
> > PKI? Dogtag PKI (aka pki-core package) is mostly written on top of the
> > Tomcat stack. As far as I know the Dogtag team is still working on Java
> > 11 support.
> >
> > Dogtag is a core component of FreeIPA, which is a one of three major
> > features of Fedora Server collection (the other two are modularity and
> > Cockpit) [0]. FreeIPA is also part of Fedora's OpenQA effort. It's
> > likely that Java 11 update is going to break a core feature of Fedora
> > and QA gating for a considerable amount of packages.
> >
> > Could you please hold of the merge of the side tag and work with the
> > Dogtag team to solve the issue?
> >
> > By the way I see a rebuild of Tomcat in the side tag but there is no
> > pki-core build. Why is pki-core missing from the tag? Is it one of the
> > FTBFS packages?
> >
> > $ koji list-tagged f33-java11 | grep tomcat
> > tomcat-9.0.36-2.fc33  f33-java11jvanek
> > tomcat-native-1.2.23-2.fc33   f33-java11jvanek
> > tomcat-taglibs-parent-3-12.fc33   f33-java11jvanek
> > tomcatjss-7.5.0-0.5.fc33  f33-java11jvanek
> > $ koji list-tagged f33-java11 | grep pki
> > 
> >
>
> pki-core fails to build in the side tag with this error:
>
>   bad class file:
> /usr/share/java/tomcatjss.jar(org/apache/tomcat/util/net/jss/IPasswordStore.class)
> class file has wrong version 55.0, should be 52.0
> Please remove or make sure it appears in the correct subdirectory
> of the classpath.
>
> That means that tomcatjss has Java 11 bytecode and I guess pki-core is
> trying to use Java 8.
>
> A quick glance at tomcatjss package shows it is built by ant with no
> sauce/target level specified at all, which means it is built with Java
> 11 bytecode by default.

(snip)

> You should fix this by rebuilding tomcatjss with Java 8 bytecode.
> Here's an example where I fixed the same problem in another package:
> https://src.fedoraproject.org/rpms/aopalliance/c/5fdc6912e39fe15fe55cedcc6392847f773d254c

Been there, tried that, it fails due to an unrelated tomcat update.
See: https://pagure.io/fesco/issue/2449#comment-666061

Fabio

> --
> Mat Booth
> http://fedoraproject.org/get-fedora
> ___
> 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
___
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