[EPEL-devel] Fedora EPEL 6 updates-testing report
The following Fedora EPEL 6 Security updates need testing: Age URL 13 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-c1577dae55 singularity-3.1.1-1.1.el6 12 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-2f5f6c5ba9 libmediainfo-19.04-1.el6 mediainfo-19.04-1.el6 12 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-612bab5fc3 drupal7-7.67-1.el6 8 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-5ff064965f drupal7-entity-1.9-1.el6 4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-50e0fd4815 drupal7-ds-2.16-1.el6 4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-fe7c636c57 drupal7-uuid-1.2-1.el6 4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-6326ff7745 drupal7-xmlsitemap-2.6-1.el6 4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-65bad7ac43 drupal7-context-3.10-1.el6 4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-5621f2527a drupal7-path_breadcrumbs-3.4-1.el6 4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-1af316b5db drupal7-module_filter-2.2-1.el6 4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-e90e3284bc drupal7-views-3.23-1.el6 The following builds have been pushed to Fedora EPEL 6 updates-testing ansible-2.6.17-1.el6 conspy-1.14-2.el6 gsi-openssh-5.3p1-20.el6 Details about builds: ansible-2.6.17-1.el6 (FEDORA-EPEL-2019-31f976103e) SSH-based configuration management, deployment, and task execution system Update Information: Update to 2.6.17 bugfix release. ChangeLog: * Tue May 28 2019 Kevin Fenzi - 2.6.17-1 - Update to 2.6.17. conspy-1.14-2.el6 (FEDORA-EPEL-2019-b3344760f7) Remote control for text mode virtual consoles Update Information: Update to latest upstream release ChangeLog: * Sat May 25 2019 Robert Scheck - 1.14-2 - Update license tag to reflect actual license * Sat May 25 2019 Fabian Affolter - 1.14-1 - Update to latest upstream release * Thu Jan 31 2019 Fedora Release Engineering - 1.8-16 - Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild * Thu Jul 12 2018 Fedora Release Engineering - 1.8-15 - Rebuilt for https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild * Wed Feb 7 2018 Fedora Release Engineering - 1.8-14 - Rebuilt for https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild * Wed Aug 2 2017 Fedora Release Engineering - 1.8-13 - Rebuilt for https://fedoraproject.org/wiki/Fedora_27_Binutils_Mass_Rebuild * Wed Jul 26 2017 Fedora Release Engineering - 1.8-12 - Rebuilt for https://fedoraproject.org/wiki/Fedora_27_Mass_Rebuild * Fri Feb 10 2017 Fedora Release Engineering - 1.8-11 - Rebuilt for https://fedoraproject.org/wiki/Fedora_26_Mass_Rebuild gsi-openssh-5.3p1-20.el6 (FEDORA-EPEL-2019-e1ccd66f69) An implementation of the SSH protocol with GSI authentication Update Information: Change GSSAPITrustDNS default to no. ChangeLog: * Tue May 28 2019 Mattias Ellert - 5.3p1-20 - Change GSSAPITrustDNS default to no ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
[EPEL-devel] Fedora EPEL 7 updates-testing report
The following Fedora EPEL 7 Security updates need testing: Age URL 287 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-3c9292b62d condor-8.6.11-1.el7 95 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-f8311ec8a2 tor-0.3.5.8-1.el7 63 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-d2c1368294 cinnamon-3.6.7-5.el7 55 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-50a6a1ddfd afflib-3.7.18-2.el7 29 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-c499781e80 python-gnupg-0.4.4-1.el7 26 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-bc0182548b bubblewrap-0.3.3-2.el7 14 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-04c7455f6a singularity-3.1.1-1.1.el7 13 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-0d44655ca3 libmediainfo-19.04-1.el7 mediaconch-18.03.2-7.el7 mediainfo-19.04-1.el7 12 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-1605b73a09 drupal7-7.67-1.el7 8 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-87fa8d93b6 drupal7-entity-1.9-1.el7 4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-b909a6e178 sleuthkit-4.6.6-1.el7 4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-9cab93353c drupal7-ds-2.16-1.el7 4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-2c1ec539fd drupal7-uuid-1.2-1.el7 4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-f614c9a4bc drupal7-xmlsitemap-2.6-1.el7 4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-8278894e4d drupal7-context-3.10-1.el7 4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-de5e3216ff drupal7-path_breadcrumbs-3.4-1.el7 4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-748b40598c drupal7-module_filter-2.2-1.el7 4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-53f9189a5e drupal7-views-3.23-1.el7 3 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-043371cfab rust-1.35.0-1.el7 The following builds have been pushed to Fedora EPEL 7 updates-testing gsi-openssh-7.4p1-4.el7 lighttpd-1.4.54-1.el7 python-lark-parser-0.7.1-1.el7 python-resultsdb_api-2.1.3-1.el7 Details about builds: gsi-openssh-7.4p1-4.el7 (FEDORA-EPEL-2019-b28a3dc752) An implementation of the SSH protocol with GSI authentication Update Information: Change GSSAPITrustDNS default to no. ChangeLog: * Tue May 28 2019 Mattias Ellert - 7.4p1-4 - Change GSSAPITrustDNS default to no lighttpd-1.4.54-1.el7 (FEDORA-EPEL-2019-17cb738520) Lightning fast webserver with light system requirements Update Information: https://www.lighttpd.net/2019/5/27/1.4.54/ ChangeLog: * Sun May 26 2019 Gwyn Ciesla - 1.4.54-1 - 1.4.54 References: [ 1 ] Bug #1714379 - lighttpd-1.4.54 is available https://bugzilla.redhat.com/show_bug.cgi?id=1714379 python-lark-parser-0.7.1-1.el7 (FEDORA-EPEL-2019-87e068191b) Lark is a modern general-purpose parsing library for Python Update Information: Bump version 0.7.1 ChangeLog: * Mon May 20 2019 Scott K Logan - 0.7.1-1 - Update to 0.7.1 References: [ 1 ] Bug #1697347 - python-lark-parser-0.7.1 is available https://bugzilla.redhat.com/show_bug.cgi?id=1697347 python-resultsdb_api-2.1.3-1.el7 (FEDORA-EPEL-2019-b5de6e68ea) Interface api to ResultsDB Update Information: Fix 'RetryError' object has no attribute 'message' ChangeLog: * Tue May 28 2019 Frantisek Zatloukal - 2.1.3-1 - Fix 'RetryError' object has no attribute 'message'
[389-devel] 389 DS nightly 2019-05-29 - 94% PASS
https://fedorapeople.org/groups/389ds/ci/nightly/2019/05/29/report-389-ds-base-1.4.1.3-20190528git3d4c48e.fc29.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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org
Re: Bodhi 4.0.0 deployed, one known issue so far
On Tue, 2019-05-28 at 20:22 -0600, Orion Poplawski wrote: > Perhaps this is the source of: > > # /etc/cron.hourly/0yum-hourly.cron > Updateinfo file is not valid XML: '/var/cache/yum/x86_64/7/epel/92f2e15cad66d79ea1ad327e2af7af89d98e4d1 > 53d7a3e27ff41946f476af5b4-updateinfo.xml.zck', > mode 'rt' at 0x7fa11cc331e0> > > https://pagure.io/releng/issue/8392 Yeah, that's a possibility since this version of Bodhi introduced zchunked updateinfo files. Maybe jdieter can shed some light on it for us in the ticket. signature.asc Description: This is a digitally signed message part ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Bodhi 4.0.0 deployed, one known issue so far
On 5/28/19 11:04 AM, Randy Barlow wrote: Greetings! I have just deployed Bodhi 4.0.0 to production: https://bodhi.fedoraproject.org/docs/user/release_notes.html One known issue has been found[0] so far: after creating an update, your browser will be redirected to a URL that does not exist. The update was created, however, and you should receive an e-mail with the URL to it (and can also see it on your user page in Bodhi). Let me know if you find any other problems! [0] https://github.com/fedora-infra/bodhi/issues/3248 Perhaps this is the source of: # /etc/cron.hourly/0yum-hourly.cron Updateinfo file is not valid XML: '/var/cache/yum/x86_64/7/epel/92f2e15cad66d79ea1ad327e2af7af89d98e4d153d7a3e27ff41946f476af5b4-updateinfo.xml.zck', mode 'rt' at 0x7fa11cc331e0> https://pagure.io/releng/issue/8392 ? -- Orion Poplawski Manager of NWRA Technical Systems 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 https://www.nwra.com/ smime.p7s Description: S/MIME Cryptographic Signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
[Bug 1714466] perl-Devel-StackTrace-2.04 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1714466 --- Comment #5 from Fedora Update System --- perl-Devel-StackTrace-2.04-2.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-a8d30d6078 -- 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1714366] perl-bareword-filehandles-0.007 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1714366 --- Comment #6 from Fedora Update System --- perl-bareword-filehandles-0.007-1.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-59cbc54fcb -- 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1711558] perl-Test2-Suite-0.000122 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1711558 Fedora Update System changed: What|Removed |Added Status|ON_QA |CLOSED Fixed In Version|perl-Test2-Suite-0.000122-1 |perl-Test2-Suite-0.000122-1 |.fc31 |.fc31 ||perl-Test2-Suite-0.000122-1 ||.fc30 Resolution|--- |ERRATA Last Closed||2019-05-29 00:49:28 --- Comment #4 from Fedora Update System --- perl-Test2-Suite-0.000122-1.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1686595] rt-4.4.4 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1686595 Fedora Update System changed: What|Removed |Added Status|ON_QA |CLOSED Fixed In Version||rt-4.4.4-1.fc30 Resolution|--- |ERRATA Last Closed||2019-05-29 00:49:18 --- Comment #5 from Fedora Update System --- rt-4.4.4-1.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1648489] Errno architecture does not match executable architecture at /usr/lib64/perl5/Errno.pm line 12
https://bugzilla.redhat.com/show_bug.cgi?id=1648489 Ben Cotton changed: What|Removed |Added Status|NEW |CLOSED Resolution|--- |EOL Last Closed||2019-05-28 23:17:39 --- Comment #8 from Ben Cotton --- Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Fedora 28 End Of Life
As of the 28th of May 2019, Fedora 28 has reached its end of life for updates and support. No further updates, including security updates, will be available for Fedora 28. Fedora 29 will continue to receive updates until approximately one month after the release of Fedora 31. The maintenance schedule of Fedora releases is documented on the Fedora Project wiki [0]. The Fedora Project wiki also contains instructions [1] on how to upgrade from a previous release of Fedora to a version receiving updates. Regards, Mohan Boddu. [0] https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule [1]https://fedoraproject.org/wiki/Upgrading?rd=DistributionUpgrades ___ 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Fedora 28 End Of Life
As of the 28th of May 2019, Fedora 28 has reached its end of life for updates and support. No further updates, including security updates, will be available for Fedora 28. Fedora 29 will continue to receive updates until approximately one month after the release of Fedora 31. The maintenance schedule of Fedora releases is documented on the Fedora Project wiki [0]. The Fedora Project wiki also contains instructions [1] on how to upgrade from a previous release of Fedora to a version receiving updates. Regards, Mohan Boddu. [0] https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule [1]https://fedoraproject.org/wiki/Upgrading?rd=DistributionUpgrades ___ 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://getfedora.org/code-of-conduct.html 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
[Bug 1714466] perl-Devel-StackTrace-2.04 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1714466 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #4 from Fedora Update System --- perl-Devel-StackTrace-2.04-2.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-6895eb202f -- 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1714366] perl-bareword-filehandles-0.007 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1714366 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #5 from Fedora Update System --- perl-bareword-filehandles-0.007-1.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-b631233169 -- 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Re: Bodhi 4.0.0 deployed, one known issue so far
Hi, I just tried to submit an update via `fedpkg update` but got a failure via the cli: $ fedpkg update Could not execute update: Could not generate update request: 'anonymous' A copy of the filled in template is saved as bodhi.template.last Nevertheless the update got submitted and is available on Bodhi (it's this one: https://bodhi.fedoraproject.org/updates/FEDORA-2019-16433c312e). Cheers, Dan Randy Barlow writes: > Greetings! > > I have just deployed Bodhi 4.0.0 to production: > > https://bodhi.fedoraproject.org/docs/user/release_notes.html > > One known issue has been found[0] so far: after creating an update, > your browser will be redirected to a URL that does not exist. The > update was created, however, and you should receive an e-mail with the > URL to it (and can also see it on your user page in Bodhi). > > Let me know if you find any other problems! > > > [0] https://github.com/fedora-infra/bodhi/issues/3248 > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
[Bug 1714796] New: perl-Workflow-1.46 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1714796 Bug ID: 1714796 Summary: perl-Workflow-1.46 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Workflow Keywords: FutureFeature, Triaged Assignee: emman...@seyman.fr Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: emman...@seyman.fr, perl-devel@lists.fedoraproject.org Target Milestone: --- Classification: Fedora Latest upstream release: 1.46 Current version/release in rawhide: 1.45-6.fc30 URL: https://metacpan.org/release/Workflow Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/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/17896/ -- 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Re: Fedora 32 Self-Contained Change proposal: Track Changes in Taiga
To address some additional questions and comments that have come up: The discoverability with this process is still good. We'll still produce either the wiki ChangeSet page or a static HTML page that contains similar information. Both options would still allow for search engines to get the content. In some ways, discoverability is improved because a page can't be "lost" by mistyping a category. There is an example change available for view: https://teams.fedoraproject.org/project/bcotton-test-changes-tracker/us/1?kanban-status=29 The idea is to separate things that are more like metadata from the content of the change itself. This allows for easier reporting and removes the need for change submitters to try to get free-form content into a parseable form. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: f30 update & bluetooth
Hi, On 5/28/19 3:26 PM, Wells, Roger K. via devel wrote: I just updated F30 via dnf update. The kernel in use went from 5.0.13-300.fc30.x86_64 to 5.0.17-300.fc30.x86_64 I regularly use two Bluetooth devices, an aging Microsoft mouse and Apple Air Pods (ear phones). Now they are both quite flaky: While moving, the mouse will connect for a few milli-seconds then disconnect. This repeats about every ten seconds. Removing the mouse and re-pairing will allow it to function for at least some hours but suspend or re-boot and one has to do it again. The Air Pods did connect but even though selected in the Sound options the sound still came from the built in speakers (at least once). Another time they did connect for a while but disconnected when the pc was idle for a half hour or so. Boot to the earlier kernel solved these issues. The pc is a Lenovo X280 thinkpad It's quite likely you're hitting a known bug[0], there is a proposed fix included in 5.1.5 which is currently in updates-testing. [0] https://bugzilla.kernel.org/show_bug.cgi?id=203643 Regards, Jeremy ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: f30 update & bluetooth
On Tue, May 28, 2019 at 1:27 PM Wells, Roger K. via devel wrote: > > I just updated F30 via dnf update. > The kernel in use went from 5.0.13-300.fc30.x86_64 to 5.0.17-300.fc30.x86_64 > I regularly use two Bluetooth devices, an aging Microsoft mouse and > Apple Air Pods (ear phones). > Now they are both quite flaky: > While moving, the mouse will connect for a few milli-seconds then > disconnect. This repeats about every ten seconds. I'm having the same problem with a bluetooth mouse. I suspect a user space regression because with these same kernels (for Fedora 30) used on Fedora 29 the problem doesn't happen. If I go to Settings > Bluetooth > double click on device, the Connection switch is "disabled" and if I set it to "enabled" it immediately flips back to "disabled" - if I do that about 12-15 times, finally it sticks and I have a connection. Bluetooth is right now my #1 complaint. This same laptop and bluetooth mouse combination works flawlessly under Windows 10. I haven't been able to isolate which of half dozen things related to Bluetooth are responsible. > Removing the mouse and re-pairing will allow it to function for at least > some hours but suspend or re-boot and one has to do it again. > The Air Pods did connect but even though selected in the Sound options > the sound still came from the built in speakers (at least once). > Another time they did connect for a while but disconnected when the pc > was idle for a half hour or so. > Boot to the earlier kernel solved these issues. Your case sounds a little different than mine if regression to a previous kernel fixes the problem. That's very straightforward to report to the bluetooth list (bugzilla.kernel.org bug reporting system is not used for bluetooth bugs you have to use the list), although the optimal way to report it is to do a kernel bisect to prove exactly which commit (or batch of them) is responsible for the regression. -- Chris Murphy ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
f30 update & bluetooth
I just updated F30 via dnf update. The kernel in use went from 5.0.13-300.fc30.x86_64 to 5.0.17-300.fc30.x86_64 I regularly use two Bluetooth devices, an aging Microsoft mouse and Apple Air Pods (ear phones). Now they are both quite flaky: While moving, the mouse will connect for a few milli-seconds then disconnect. This repeats about every ten seconds. Removing the mouse and re-pairing will allow it to function for at least some hours but suspend or re-boot and one has to do it again. The Air Pods did connect but even though selected in the Sound options the sound still came from the built in speakers (at least once). Another time they did connect for a while but disconnected when the pc was idle for a half hour or so. Boot to the earlier kernel solved these issues. The pc is a Lenovo X280 thinkpad -- Roger Wells, P.E. leidos 221 Third St Newport, RI 02840 401-847-4210 (voice) 401-849-1585 (fax) roger.k.we...@leidos.com ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
[Bug 1450364] read_file(, binmode => ':utf8') produces warnings
https://bugzilla.redhat.com/show_bug.cgi?id=1450364 Ben Cotton changed: What|Removed |Added Status|NEW |CLOSED Resolution|--- |EOL Last Closed||2019-05-28 19:24:35 --- Comment #8 from Ben Cotton --- Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Re: Fedora 30 Not Working on Omen with nVidia
On Tue, 28 May 2019 18:09:50 - "Personalized Marketing Inc" wrote: > Hello, I have tried to install Fedora 28, 29, and 30 on my HP Omen > with nVidia Graphics. Fedora 28 and 29 had issues with the Keyboard, > Fedora 30 tested just fine from the USB drive however after > installing it, the system would not go past the login screen. No > functions on the keyboard or mouse worked either. > > I loved Fedora 26 and would love to use Fedora 30 over Windows 10. Is > there a patch that needs installed while using the trial USB drive? > Any thoughts or driver programs that I need to install with it? > > I know that other Linux Editions have nVidia Graphics included in the > IOS and wondered if Fedora had similar? Fedora doesn't package in the main project any software that has a non-free license. There are other repositories that do package such software, the primary one being rpmfusion.org. They package the binary blob from nvidia, and a utility called akmod that builds it into a module for the linux kernel. You can find more information here: https://rpmfusion.org/ In particular, it is possible to enable those repositories so that doing an update of Fedora pulls in any updates of their packages. https://rpmfusion.org/Configuration I'm not sure that this will fix your issue. You are actually asking on the wrong list, this is really a users issue, so you should post it on one of the following with a detailed description: The users mailing list, Community support for Fedora users or the web based help interface, https://ask.fedoraproject.org/c/english These are independent of each other. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Fedora 30 Not Working on Omen with nVidia
Hello, I have tried to install Fedora 28, 29, and 30 on my HP Omen with nVidia Graphics. Fedora 28 and 29 had issues with the Keyboard, Fedora 30 tested just fine from the USB drive however after installing it, the system would not go past the login screen. No functions on the keyboard or mouse worked either. I loved Fedora 26 and would love to use Fedora 30 over Windows 10. Is there a patch that needs installed while using the trial USB drive? Any thoughts or driver programs that I need to install with it? I know that other Linux Editions have nVidia Graphics included in the IOS and wondered if Fedora had similar? ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Packages retirement as part of OpenStack clients updates in Rawhide
On Thu, May 16, 2019 at 11:38 AM Alfredo Moralejo Alonso < amora...@redhat.com> wrote: > Hi, > > OpenStack client packages have been updated in Fedora Rawhide to the > latest releases included in recently published Stein version. > > As part of this update some packages which were required in the past are > not longer needed, so i plan to retire them from Fedora: > > python-automaton > python-castellan > python-ceilometermiddleware > python-cursive > python-keystonemiddleware > python-microversion-parse > python-oslo-cache > python-oslo-concurrency > python-oslo-messaging > python-oslo-middleware > python-oslo-policy > python-oslo-privsep > python-oslo-reports > python-oslo-rootwrap > python-oslo-service > python-oslo-sphinx > python-oslo-vmware > python-osprofiler > python-os-win > python-pycadf > python-reno > python-taskflow > > Finally, openstack clients updates is done in rawhide, the list of retired packages is: python-ceilometermiddleware python-keystonemiddleware python-os-win python-oslo-vmware python-pycadf python-oslo-cache python-cursive python-castellan python-oslo-rootwrap python-oslo-middleware python-oslo-policy python-oslo-reports python-oslo-privsep python-microversion-parse python-osprofiler python-oslo-messaging python-oslo-service Best regards, Alfredo According to repoqueries to rawhide, these packages are not longer needed > for any other package so it should be safe to get them out but let me know > if anything else is needing them in. > > Best regards, > > Alfredo > > > ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
[EPEL-devel] [Fedocal] Reminder meeting : EPEL Steering Co
Dear all, You are kindly invited to the meeting: EPEL Steering Co on 2019-05-29 from 18:00:00 to 19:00:00 GMT At freenode@fedora-meeting The meeting will be about: This is the weekly EPEL Steering Committee Meeting. Agenda is in the https://infinote.fedoraproject.org/cgit/infinote/tree/epel-meeting-next Source: https://apps.fedoraproject.org/calendar/meeting/9364/ ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
Bodhi 4.0.0 deployed, one known issue so far
Greetings! I have just deployed Bodhi 4.0.0 to production: https://bodhi.fedoraproject.org/docs/user/release_notes.html One known issue has been found[0] so far: after creating an update, your browser will be redirected to a URL that does not exist. The update was created, however, and you should receive an e-mail with the URL to it (and can also see it on your user page in Bodhi). Let me know if you find any other problems! [0] https://github.com/fedora-infra/bodhi/issues/3248 signature.asc Description: This is a digitally signed message part ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Fedora 31 System-Wide Change proposal: Node.js 12.x by default
https://fedoraproject.org/wiki/Changes/Nodejs12x == Summary == The latest release of Node.js to carry a 30-month lifecycle is the 12.x series. As with 10.x and 8.x before it, Fedora 31 will carry 12.x as the default Node.js interpreter for the system. The 10.x interpreter will remain available as a non-default module stream. == Owner == * Name: [[User:Sgallagh| Stephen Gallagher]] * Email: sgall...@fedoraproject.org * Responsible SIG: Node.js SIG == Detailed Description == Fedora 31 will ship with the latest LTS version of Node.js by default. This will either be the `nodejs:12` module stream or else replicated to the non-modular repository, depending on the status of other release engineering work around supporting modular content in the non-modular buildroots. To end-users, the experience should be identical: `dnf install nodejs` will give them `nodejs-12.x` and the matching `npm` package. == Benefit to Fedora == Node.js is a popular server-side JavaScript engine. Keeping Fedora on the latest release allows us to continue tracking the state-of-the-art in that space. For those whose applications do not yet work with the 12.x release, Fedora 31 will also have the 10.x release available as a selectable module stream. == Scope == * Proposal owners: The packages are already built for Fedora 31 in a non-default module stream. On June 14th, 2019, the nodejs-12.x packages will become the default in Fedora 31 (either by making the 12.x module stream be the default stream or by rebuilding the packages as non-modular , depending on other factors). If the non-modular buildroot work is finished and available by July 17th (a week before the mass-rebuild), Node.js 12.x will drop the non-modular packages and make the 12.x stream the default. * Other developers: Any developer with a package that depends on Node.js at run-time or build-time should test with the 12.x module stream enabled as soon as possible. Issues should be reported to nod...@lists.fedoraproject.org * Release engineering: [https://pagure.io/releng/issue/8388 #8388] Release engineering and FESCo will need to approve the change to the default module stream. * Policies and guidelines: N/A (not needed for this Change) * Trademark approval: N/A (not needed for this Change) == Upgrade/compatibility impact == As with previous releases, users running Fedora 29 or Fedora 30 with the non-modular nodejs-10.x packages will be automatically upgraded to the 12.x packages, which may cause issues. If users are running software known not to support Node.js 12.x yet, they can switch the system back to using 10.x with yum commands (to be documented in release notes). == How To Test == * Confirm that `yum install nodejs` results in Node.js 12.x being installed. * Confirm that upgrading from Fedora 29 or Fedora 30 with nodejs-10.x installed (non-modular) results in an upgrade to nodejs-12.x * Confirm that upgrading from Fedora 29 or Fedora 30 with the `nodejs:10` module enabled does *not* result in an upgrade to 12.x and still has `nodejs:10` enabled on Fedora 31. * Confirm that upgrading from Fedora 29 or Fedora 30 with the `nodejs:12` module enabled upgrades successfully and still has `nodejs:12` enabled on Fedora 31. == User Experience == Users will have the 12.x release of Node.js available by default. See the "Upgrade/compatibility impact" section for specific details. == Dependencies == All packages prefixed with `nodejs-` depend on this package. They will need to be updated or removed from Fedora 31 if they do not work with Node.js 12.x. == Contingency Plan == * Contingency mechanism: Revert to Node.js 10.x as the default stream. This may require bumping epoch or making the `nodejs:10` stream the default, depending on the status of the modules-in-non-modular-buildroot work at the time. * Contingency deadline: August 5th, 2019 * Blocks release? No == Documentation == * https://nodejs.org/dist/latest-v12.x/docs/api/ * https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V12.md == Release Notes == Fedora 31 now ships with Node.js 12.x as the default Node.js JavaScript server-side engine. If your applications are not yet ready for this newer version, you can revert to the 10.x series by running the following commands dnf remove nodejs dnf module reset nodejs dnf module install nodejs:10 -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Fedora 31 System-Wide Change proposal: Node.js 12.x by default
https://fedoraproject.org/wiki/Changes/Nodejs12x == Summary == The latest release of Node.js to carry a 30-month lifecycle is the 12.x series. As with 10.x and 8.x before it, Fedora 31 will carry 12.x as the default Node.js interpreter for the system. The 10.x interpreter will remain available as a non-default module stream. == Owner == * Name: [[User:Sgallagh| Stephen Gallagher]] * Email: sgall...@fedoraproject.org * Responsible SIG: Node.js SIG == Detailed Description == Fedora 31 will ship with the latest LTS version of Node.js by default. This will either be the `nodejs:12` module stream or else replicated to the non-modular repository, depending on the status of other release engineering work around supporting modular content in the non-modular buildroots. To end-users, the experience should be identical: `dnf install nodejs` will give them `nodejs-12.x` and the matching `npm` package. == Benefit to Fedora == Node.js is a popular server-side JavaScript engine. Keeping Fedora on the latest release allows us to continue tracking the state-of-the-art in that space. For those whose applications do not yet work with the 12.x release, Fedora 31 will also have the 10.x release available as a selectable module stream. == Scope == * Proposal owners: The packages are already built for Fedora 31 in a non-default module stream. On June 14th, 2019, the nodejs-12.x packages will become the default in Fedora 31 (either by making the 12.x module stream be the default stream or by rebuilding the packages as non-modular , depending on other factors). If the non-modular buildroot work is finished and available by July 17th (a week before the mass-rebuild), Node.js 12.x will drop the non-modular packages and make the 12.x stream the default. * Other developers: Any developer with a package that depends on Node.js at run-time or build-time should test with the 12.x module stream enabled as soon as possible. Issues should be reported to nod...@lists.fedoraproject.org * Release engineering: [https://pagure.io/releng/issue/8388 #8388] Release engineering and FESCo will need to approve the change to the default module stream. * Policies and guidelines: N/A (not needed for this Change) * Trademark approval: N/A (not needed for this Change) == Upgrade/compatibility impact == As with previous releases, users running Fedora 29 or Fedora 30 with the non-modular nodejs-10.x packages will be automatically upgraded to the 12.x packages, which may cause issues. If users are running software known not to support Node.js 12.x yet, they can switch the system back to using 10.x with yum commands (to be documented in release notes). == How To Test == * Confirm that `yum install nodejs` results in Node.js 12.x being installed. * Confirm that upgrading from Fedora 29 or Fedora 30 with nodejs-10.x installed (non-modular) results in an upgrade to nodejs-12.x * Confirm that upgrading from Fedora 29 or Fedora 30 with the `nodejs:10` module enabled does *not* result in an upgrade to 12.x and still has `nodejs:10` enabled on Fedora 31. * Confirm that upgrading from Fedora 29 or Fedora 30 with the `nodejs:12` module enabled upgrades successfully and still has `nodejs:12` enabled on Fedora 31. == User Experience == Users will have the 12.x release of Node.js available by default. See the "Upgrade/compatibility impact" section for specific details. == Dependencies == All packages prefixed with `nodejs-` depend on this package. They will need to be updated or removed from Fedora 31 if they do not work with Node.js 12.x. == Contingency Plan == * Contingency mechanism: Revert to Node.js 10.x as the default stream. This may require bumping epoch or making the `nodejs:10` stream the default, depending on the status of the modules-in-non-modular-buildroot work at the time. * Contingency deadline: August 5th, 2019 * Blocks release? No == Documentation == * https://nodejs.org/dist/latest-v12.x/docs/api/ * https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V12.md == Release Notes == Fedora 31 now ships with Node.js 12.x as the default Node.js JavaScript server-side engine. If your applications are not yet ready for this newer version, you can revert to the 10.x series by running the following commands dnf remove nodejs dnf module reset nodejs dnf module install nodejs:10 -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Node.js 12.x Plans for F31+
On Mon, May 27, 2019 at 6:59 AM Vít Ondruch wrote: > > > Dne 24. 05. 19 v 21:00 Stephen Gallagher napsal(a): > > On Tue, Apr 23, 2019 at 5:40 PM Stephen Gallagher > > wrote: > >> Today, the Node.js upstream released 12.0.0, the next in its line of > >> long-term support releases. I plan to make this the default version of > >> Node.js in Fedora 31+, but not immediately. I'm currently working on > >> getting a modular version of 12.x built for F29, F30 and Rawhide. I'll > >> get that out to updates-testing this week. I'll send out an update > >> once it's pushed to updates-testing. > >> > >> Once that's available, I encourage all NPM packagers in Fedora to > >> start testing their build and runtime with the 12.x module. I will be > >> filing a Change Proposal and plan to switch the system interpreter for > >> Rawhide over to 12.x around the end of May or beginning of June. > >> > >> The exact timing may depend on the current status of the > >> modules-in-the-non-modular-buildroot work in Fedora. If that's > >> available by this time, I will retire the non-modular Node.js > >> interpreter package and make the 12.x module the default stream for > >> F31+. If it's not available, I'll continue to do what I've been doing > >> in F29 and F30; building both the modular and non-modular packages. > >> > >> If you discover that you own NPM packages that are critical and do not > >> work with Node.js 12.x, please inform me immediately. We'll talk with > >> upstream and see what we can do about it. > > I plan to make this switch on Friday, May 31st, so if you have > > packages that may break, now would be a good time to let me know. > > > > Since the buildroot work isn't yet completely ready, I'm going to take > > the stop-gap approach and merge the '12' branch to master and do a > > non-modular build of Node.js 12.x in Rawhide on that day. > > > I might be missing something, but you promised "I will be filing a > Change Proposal" in your original email above. Was it filled? Was it > approved? You are correct; I forgot to file the Change I promised. *sigh* Filing it now and I will move out the cut-over date to June 14th to give enough time for it to be approved. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
[Bug 1714466] perl-Devel-StackTrace-2.04 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1714466 --- Comment #3 from Fedora Update System --- perl-Devel-StackTrace-2.04-2.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-a8d30d6078 -- 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1714466] perl-Devel-StackTrace-2.04 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1714466 Fedora Update System changed: What|Removed |Added Status|NEW |MODIFIED --- Comment #2 from Fedora Update System --- perl-Devel-StackTrace-2.04-2.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-6895eb202f -- 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://getfedora.org/code-of-conduct.html 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
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. This report is online at: https://churchyard.fedorapeople.org/orphans-2019-05-27.txt Packages retired today but still in this report: rubygem-sprite-factory Request package ownership via: https://pagure.io/releng/issues Package (co)maintainers Status Change aeskulap orphan 6 weeks ago apache-commons-discovery lkundrak, mizdebsk, orphan, 0 weeks ago spike ceph-deploy branto, fsimonce, ktdreyer, 3 weeks ago orphan, trhoden checkstyledbhole, greghellings, lef, 1 weeks ago mizdebsk, nsantos, orphan, rmyers clpbardcantrel, orphan 3 weeks ago cmdtest orphan 0 weeks ago compat-openssl10-pkcs11-helperorphan, rdieter 2 weeks ago dvdbackup cicku, orphan6 weeks ago emacs-pymacs orphan 6 weeks ago flr orphan 0 weeks ago genbackupdata orphan 0 weeks ago gnome-dvb-daemon orphan 6 weeks ago gnome-shell-extension-panel-osd orphan 6 weeks ago gnumed-server orphan 0 weeks ago gpart dcantrel, orphan 3 weeks ago gscribble orphan 0 weeks ago h2akurtakov, dchen, lef, orphan3 weeks ago jwebunit orphan 2 weeks ago kimchijcapik, orphan 0 weeks ago librtfcomporphan 0 weeks ago loopabull orphan 0 weeks ago lrbd orphan 0 weeks ago ltspfsenslaver, orphan 5 weeks ago monkeysphere ctubbsii, orphan 1 weeks ago ninja-ide echevemaster, orphan 5 weeks ago nodejs-array-uniq nodejs-sig, orphan 0 weeks ago pdc-updater orphan 0 weeks ago plaguedcbw, orphan 4 weeks ago pyqt-mail-checker orphan 0 weeks ago python-cachy orphan 1 weeks ago python-larch orphan 0 weeks ago python-mandrill orphan 0 weeks ago python-psphereimcleod, orphan 0 weeks ago python-pylev orphan 1 weeks ago python-pytest-testmon orphan, python-sig 1 weeks ago pywebkitgtk ivazquez, orphan, walters5 weeks ago repoview orphan 0 weeks ago rubygem-chunky_pngmmorsi, orphan 6 weeks ago rubygem-codemirror-rails orphan 5 weeks ago rubygem-commander maxamillion, orphan, tdawson 3 weeks ago rubygem-compass-960-pluginorphan 6 weeks ago rubygem-jquery-ui-rails orphan 3 weeks ago rubygem-paranoia orphan 2 weeks ago rubygem-sprite-factory * orphan 7 weeks ago rubygem-webratmmorsi, orphan 6 weeks ago system-config-firewallorphan, twoerner 3 weeks ago testoob orphan 2 weeks ago totpcgi herlo, kevin, orphan 0 weeks ago transmission-remote-cli orphan
Re: C++ help needed fixing VXL on 32 bit architectures
On 5/28/19 2:26 PM, Roberto Ragusa wrote: On 5/28/19 1:57 AM, John Reiser wrote: if ((t&=7)==0) *++ib=0; int a; (*vs_) >> a; if (a) *ib|=static_cast(1<<(7-t)); } Such code is an abomination for lack of clarity. Also, the preceding line for (int x=0,t=0; x Isn't t forced into 0..6 by the t&=7 evaluation in the first if? 0..7, sorry for mistyping. -- Roberto Ragusamail at robertoragusa.it ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: C++ help needed fixing VXL on 32 bit architectures
On 5/28/19 1:57 AM, John Reiser wrote: if ((t&=7)==0) *++ib=0; int a; (*vs_) >> a; if (a) *ib|=static_cast(1<<(7-t)); } Such code is an abomination for lack of clarity. Also, the preceding line for (int x=0,t=0; x Isn't t forced into 0..6 by the t&=7 evaluation in the first if? -- Roberto Ragusamail at robertoragusa.it ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: rpmlint warning: crypto-policy-non-compliance-gnutls-1
On Mon, May 27, 2019 at 3:00 PM Tomas Mraz wrote: > > Anderson, FYI. Could you please answer the question below? > > On Fri, 2019-05-24 at 17:58 +0100, Richard W.M. Jones wrote: > > > libnbd.x86_64: W: crypto-policy-non-compliance-gnutls-1 > > > /usr/lib64/libnbd.so.0.0.0 gnutls_priority_set_direct > > > This application package calls a function to explicitly set crypto > > > ciphers for > > > SSL/TLS. That may cause the application not to use the system-wide > > > set > > > cryptographic policy and should be modified in accordance to: > > > https://fedoraproject.org/wiki/Packaging:CryptoPolicies > > > > The library does call gnutls_priority_set_direct, but in a way which > > I > > believe still uses the system policies: > > > > %prep > > ./configure --with-tls-priority=@LIBNBD,SYSTEM > > > > sets ... > > > > #define TLS_PRIORITY "@LIBNBD,SYSTEM" > > > > which calls ... > > > > err = gnutls_priority_set_direct (session, TLS_PRIORITY, NULL); > > > > So we're good and we can ignore this warning, right? > > > > I should note that I copied this coding pattern from libvirt. It looks good to me. The rpmlint shouldn't have warned there however. It seems that it incorrectly checks for SYSLOG string instead of SYSTEM. https://src.fedoraproject.org/rpms/rpmlint/blob/master/f/rpmlint.config#_475 regards, Nikos ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Review swap - zeal
I can review it without swap. вт, 28 мая 2019 г. в 13:55, Lumir Balhar : > > Hello. > > I'd like to claim ownership of retired package zeal, which is currently > in weird state not available in F30. > > Original bug: https://bugzilla.redhat.com/show_bug.cgi?id=1701666 > Review request: https://bugzilla.redhat.com/show_bug.cgi?id=1711898 > > Will take a review in exchange for something of similar complexity. > > Lumír > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Review swap - zeal
Hello. I'd like to claim ownership of retired package zeal, which is currently in weird state not available in F30. Original bug: https://bugzilla.redhat.com/show_bug.cgi?id=1701666 Review request: https://bugzilla.redhat.com/show_bug.cgi?id=1711898 Will take a review in exchange for something of similar complexity. Lumír ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Announcing Fedora CI SIG
Hi, all, I created a poll for the meeting time http://whenisgood.net/kdd4zmq Please add you votes. Proposed agenda for the first meeting: * Introduction round Who are you and what do you like to work on? (optional) * Organization matters Meeting agenda, task trackers, communication channels, fas groups.. * Open floor -- Aleksandra Fedorova bookwar ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
[Bug 1712800] Upgrade perl-Promises to 1.00
https://bugzilla.redhat.com/show_bug.cgi?id=1712800 Jitka Plesnikova changed: What|Removed |Added Depends On||1714511 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1714511 [Bug 1714511] Review Request: perl-Sub-Attribute - Reliable subroutine attribute handlers -- 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Re: C++ help needed fixing VXL on 32 bit architectures
Hi John, On Mon, May 27, 2019 16:57:18 -0700, John Reiser wrote: > > https://github.com/vxl/vxl/issues/638 > > Independent of that particular issue, it is hard to believe the claim > "vxl: A multi-platform collection of C++ software libraries ...". > They're not making a good-faith effort to be portable. From what I've seen, VXL seems to be one of those libraries that was written long long ago and has for most of its life cycle been in "maintenance mode" to somehow keep it running. For example, my PR to version the shared objects was only merged last week (!), and the super spammy nightly commit bot is still active: https://github.com/vxl/vxl/issues/624 https://github.com/vxl/vxl/pull/626 https://github.com/vxl/vxl/issues/97 Most of this is probably because the core dev community is extremely stretched. They don't have the cycles to make required updates, which, for example, is why VXL still uses a dcmtk version from 2002 (and we have no choice but to bundle it): https://github.com/vxl/vxl/issues/550 So, if you do have the time, please file these issues (or PRs if you have even more time). That'll at least make them aware of them and maybe it'll encourage others to help the dev team too. I'd like to look into all of this, but as soon as I get VXL built, I've got to work on all the tools that depend on it and are currently broken also. -- Thanks, Regards, Ankur Sinha "FranciscoD" https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Self Introduction: Gordon Messmer
Hi Gordon and welcome! So nice of you to package Bender. Would anyone be willing to sponsor Gordon? Tomas On Tue, May 28, 2019 at 7:58 AM Gordon Messmer wrote: > > Hello, > > My name is Gordon Messmer. I've been a long-time user of Red Hat > systems, starting with Red Hat Linux 4.2 in 1997. I've been packaging > software in rpm format for use in business environments for very nearly > as long. I've also been a semi-active member of the Red Hat and Fedora > mailing lists most of those years. > > My first contribution will be ansible-bender: a tool that builds > container images using ansible playbooks. > > https://bugzilla.redhat.com/show_bug.cgi?id=1714377 > > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: C++ help needed fixing VXL on 32 bit architectures
Dear Jerry, On Mon, May 27, 2019 15:33:42 -0600, Jerry James wrote: > On Mon, May 27, 2019 at 2:54 PM Jerry James wrote: > > It looks like the first few errors, at least, were fixed the day after > > the last release, in this commit: > > > > https://github.com/vxl/vxl/commit/c3fd27959f51e0469a7a6075e975f245ac306f3d > > > > You might try adding that as a patch and see if that is sufficient, or > > if there are more problems. > > I did a local mock build for i386 with that patch, and it succeeded. FYI. Ah! Thanks so much! This turned out a lot simpler than I'd feared. I hadn't even begun wading through the commit history yet. I'll go patch-build-update now. -- Thanks, Regards, Ankur Sinha "FranciscoD" https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
[Bug 1714466] perl-Devel-StackTrace-2.04 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1714466 --- Comment #1 from Upstream Release Monitoring --- Skipping the scratch build because an SRPM could not be built: ['fedpkg', '--user hotness', 'sources'] returned 2: b'' -- 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1714466] New: perl-Devel-StackTrace-2.04 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1714466 Bug ID: 1714466 Summary: perl-Devel-StackTrace-2.04 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Devel-StackTrace Keywords: FutureFeature, Triaged Assignee: rc040...@freenet.de Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: lxt...@gmail.com, p...@city-fan.org, perl-devel@lists.fedoraproject.org, rc040...@freenet.de, st...@silug.org Target Milestone: --- Classification: Fedora Latest upstream release: 2.04 Current version/release in rawhide: 2.03-5.fc30 URL: http://search.cpan.org/dist/Devel-StackTrace/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/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/11840/ -- 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1713793] perl-Code-TidyAll-0.74 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1713793 Jitka Plesnikova changed: What|Removed |Added Status|NEW |CLOSED Fixed In Version||perl-Code-TidyAll-0.74-1.fc ||31 Resolution|--- |RAWHIDE Last Closed||2019-05-28 07:34:01 -- 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1714419] ack-3.0.0 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1714419 Robin Lee changed: What|Removed |Added Status|NEW |CLOSED Fixed In Version||ack-3.0.0-1.fc31 Resolution|--- |RAWHIDE Last Closed||2019-05-28 07:29:39 -- 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1714366] perl-bareword-filehandles-0.007 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1714366 --- Comment #3 from Fedora Update System --- perl-bareword-filehandles-0.007-1.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-b631233169 -- 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1714366] perl-bareword-filehandles-0.007 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1714366 --- Comment #4 from Fedora Update System --- perl-bareword-filehandles-0.007-1.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2019-361d101a77 -- 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1714366] perl-bareword-filehandles-0.007 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1714366 --- Comment #2 from Fedora Update System --- perl-bareword-filehandles-0.007-1.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-59cbc54fcb -- 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1714366] perl-bareword-filehandles-0.007 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1714366 Petr Pisar changed: What|Removed |Added Status|ASSIGNED|MODIFIED Fixed In Version||perl-bareword-filehandles-0 ||.007-1.fc31 --- 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Re: Self Introduction: Gordon Messmer
Hi Gordon, Welcome to Fedora! On 5/28/19 8:58 AM, Gordon Messmer wrote: Hello, My name is Gordon Messmer. I've been a long-time user of Red Hat systems, starting with Red Hat Linux 4.2 in 1997. I've been packaging software in rpm format for use in business environments for very nearly as long. I've also been a semi-active member of the Red Hat and Fedora mailing lists most of those years. My first contribution will be ansible-bender: a tool that builds container images using ansible playbooks. https://bugzilla.redhat.com/show_bug.cgi?id=1714377 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
