Re: Fedora Copr builders updated to Fedora 38
On Sat, Jun 10, 2023 at 4:36 PM Kevin Kofler via devel wrote: > Considering that Fedora buildroots always get killed off within days of the > EOL, I do not see why you are keeping epel-6 buildroots active 2½ years (!) > after its EOL. Well, EL6 ELS support is still available for (around) another year, so it is a nice to have to support those limping along with EL6, but I would generally agree with the principal that if supporting a product past official EOL becomes overly onerous that support should end, or be explicitly funded out of the ELS fees if the ELS community needs that support. I do not consider setting gpgcheck=0 overly onerous for EPEL6, but I do think we should want to avoid such actions becoming the expected behavior for the next time (and there will be a next time), where the workarounds might require a much bigger effort. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[EPEL-devel] Fedora EPEL 8 updates-testing report
The following Fedora EPEL 8 Security updates need testing: Age URL 3 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-d55abd83c7 perl-HTML-StripScripts-1.06-22.el8 3 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-e14003b86d syncthing-1.23.5-1.el8 1 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-3dd846c7ab radare2-5.8.6-1.el8 1 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-c018b37680 chromium-114.0.5735.106-1.el8 The following builds have been pushed to Fedora EPEL 8 updates-testing tio-2.6-1.el8 Details about builds: tio-2.6-1.el8 (FEDORA-EPEL-2023-892bec0124) Simple TTY terminal I/O application Update Information: # tio v2.6* Remove warning when using pattern option* Add `--log-append` option Add `--log-append` option which makes tio append to any existing log file. This also changes the default behaviour of tio from appending to overwriting any existing log file. Now you have to use this new option to make tio append.* Update man page* Update `README`* Fix line termination for response wait feature The response wait feature waited for a line response, a string terminated with either `CR` or `NL`. However, some devices may send a `CR` and then their line content and then `NL`. This means `tio` will quit before receiving and printing the line response. To solve this we simply ignore the `CR` character and only consider lines terminated with a `NL` character. This should work for all devices as lines are AFAIK always terminated with either `CRNL` or a `NL`.* Update tty device listing configuration Cleanup and add FreeBSD tty device listing support.* Move map variables to tty to keep them all in one spot* Configure socket mapping flags from tty parsing logic. Remove duplicate parsing logic in socket* Support input mapping modes for sockets* Various spelling fixes* avoid "warning: unused parameter" on setspeed stub* use right `/dev/` path on Haiku* Update `README` with details on snap confinement ChangeLog: * Sat Jun 10 2023 Robert Scheck 2.6-1 - Upgrade to 2.6 (#2213990) * Sat Jan 21 2023 Fedora Release Engineering - 2.5-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild References: [ 1 ] Bug #2213990 - tio-2.6 is available https://bugzilla.redhat.com/show_bug.cgi?id=2213990 ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[EPEL-devel] Fedora EPEL 7 updates-testing report
The following Fedora EPEL 7 Security updates need testing: Age URL 3 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-becb7041de perl-HTML-StripScripts-1.06-22.el7 1 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-423bcaf739 radare2-5.8.6-1.el7 1 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-787571a7ba chromium-114.0.5735.106-1.el7 The following builds have been pushed to Fedora EPEL 7 updates-testing tio-2.6-1.el7 Details about builds: tio-2.6-1.el7 (FEDORA-EPEL-2023-6671dbf6ac) Simple TTY terminal I/O application Update Information: # tio v2.6* Remove warning when using pattern option* Add `--log-append` option Add `--log-append` option which makes tio append to any existing log file. This also changes the default behaviour of tio from appending to overwriting any existing log file. Now you have to use this new option to make tio append.* Update man page* Update `README`* Fix line termination for response wait feature The response wait feature waited for a line response, a string terminated with either `CR` or `NL`. However, some devices may send a `CR` and then their line content and then `NL`. This means `tio` will quit before receiving and printing the line response. To solve this we simply ignore the `CR` character and only consider lines terminated with a `NL` character. This should work for all devices as lines are AFAIK always terminated with either `CRNL` or a `NL`.* Update tty device listing configuration Cleanup and add FreeBSD tty device listing support.* Move map variables to tty to keep them all in one spot* Configure socket mapping flags from tty parsing logic. Remove duplicate parsing logic in socket* Support input mapping modes for sockets* Various spelling fixes* avoid "warning: unused parameter" on setspeed stub* use right `/dev/` path on Haiku* Update `README` with details on snap confinement ChangeLog: * Sat Jun 10 2023 Robert Scheck 2.6-1 - Upgrade to 2.6 (#2213990) * Sat Jan 21 2023 Fedora Release Engineering - 2.5-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild References: [ 1 ] Bug #2213990 - tio-2.6 is available https://bugzilla.redhat.com/show_bug.cgi?id=2213990 ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[EPEL-devel] Fedora EPEL 9 updates-testing report
The following Fedora EPEL 9 Security updates need testing:
Age URL
5 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-f04011e9d4
yarnpkg-1.22.19-5.el9
3 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-de31cb6120
perl-HTML-StripScripts-1.06-22.el9
3 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-a1ed86449c
syncthing-1.23.5-1.el9
1 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-e6d2f056c2
radare2-5.8.6-1.el9
1 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-5b8cf596eb
chromium-114.0.5735.106-1.el9
The following builds have been pushed to Fedora EPEL 9 updates-testing
gpaw-23.6.0-1.el9
libomemo-c-0.5.0-2.el9
tio-2.6-1.el9
tomlplusplus-3.3.0-3.el9
Details about builds:
gpaw-23.6.0-1.el9 (FEDORA-EPEL-2023-a52f11a38d)
A grid-based real-space PAW method DFT code
Update Information:
New upstream release
ChangeLog:
* Fri Jun 9 2023 Marcin Dulak - 23.6.0-1
- New upstream release
- Remove references to blacs
* Thu Jan 19 2023 Marcin Dulak - 22.8.0-5
- Exlude %{ix86} due to bug #2142304
* Thu Jan 19 2023 Fedora Release Engineering -
22.8.0-4
- Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild
* Mon Oct 24 2022 Marcin Dulak - 22.8.0-3
- Rebuild for libxc-6.0.0 on f38
* Wed Oct 12 2022 Marcin Dulak - 22.8.0-2
- Glob for build/lib platform name https://gitlab.com/gpaw/gpaw/-/issues/612
* Wed Oct 12 2022 Marcin Dulak - 22.8.0-1
- New upstream release
* Thu Jul 21 2022 Fedora Release Engineering -
22.1.0-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild
* Tue Jun 21 2022 Marcin Dulak - 22.2.0-2
- Rebuild for Python 3.11 on Fedora 37
* Fri Jan 28 2022 Marcin Dulak - 22.1.0-1
- New upstream release
- Add br fftw-devel
* Thu Jan 20 2022 Fedora Release Engineering -
21.6.0-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_36_Mass_Rebuild
* Tue Aug 3 2021 Marcin Dulak - 21.6.0-1
- New upstream release
* Thu Jul 22 2021 Fedora Release Engineering -
21.1.0-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_35_Mass_Rebuild
libomemo-c-0.5.0-2.el9 (FEDORA-EPEL-2023-aff987f90e)
Fork of libsignal-protocol-c adding support for OMEMO XEP-0384 0.5.0+
Update Information:
add patches
ChangeLog:
* Sat Jun 10 2023 topazus - 0.5.0-2
- add patches
* Sat Jun 10 2023 topazus - 0.5.0-1
- initial import from rhbz#2212599
tio-2.6-1.el9 (FEDORA-EPEL-2023-dcb0c32265)
Simple TTY terminal I/O application
Update Information:
# tio v2.6* Remove warning when using pattern option* Add `--log-append`
option Add `--log-append` option which makes tio append to any existing log
file. This also changes the default behaviour of tio from appending to
overwriting any existing log file. Now you have to use this new option to make
tio append.* Update man page* Update `README`* Fix line termination
for response wait feature The response wait feature waited for a line
response, a string terminated with either `CR` or `NL`. However, some devices
may send a `CR` and then their line content and then `NL`. This means `tio` will
quit before receiving and printing the line response. To solve this we simply
ignore the `CR` character and only consider lines terminated with a `NL`
character. This should work for all devices as lines are AFAIK always
terminated with either `CRNL` or a `NL`.* Update tty device listing
configuration Cleanup and add FreeBSD tty device listing support.* Move
map variables to tty to keep them all in one spot* Configure socket mapping
flags from tty parsing logic. Remove duplicate parsing logic in socket*
Support input mapping modes for sockets* Various spelling fixes* avoid
"warning: unused parameter" on setspeed stub* use right `/dev/` path on
Haiku* Update `README` with details on snap confinement
ChangeLog:
* Sat Jun 10 2023 Robert Scheck 2.6-1
- Upgrade to 2.6 (#2213990)
* Sat Jan 21 2023 Fedora Release Engineering - 2.5-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild
[Bug 2177932] perl-Net-DNS-1.38 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2177932 Fedora Update System changed: What|Removed |Added Fixed In Version|perl-Net-DNS-1.38-2.fc39|perl-Net-DNS-1.38-2.fc39 |perl-Net-DNS-1.39-1.fc37|perl-Net-DNS-1.39-1.fc37 ||perl-Net-DNS-1.39-1.fc38 --- Comment #18 from Fedora Update System --- FEDORA-2023-ae600320ff has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2177932 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202177932%23c18 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2177932] perl-Net-DNS-1.38 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2177932 Fedora Update System changed: What|Removed |Added Fixed In Version|perl-Net-DNS-1.38-2.fc39|perl-Net-DNS-1.38-2.fc39 ||perl-Net-DNS-1.39-1.fc37 --- Comment #17 from Fedora Update System --- FEDORA-2023-e38e484771 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2177932 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202177932%23c17 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Test-Announce] 2023-06-12 @ 15:00 UTC - Fedora QA Meeting
# Fedora Quality Assurance Meeting # Date: 2023-06-12 # Time: 15:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: #fedora-meeting on irc.libera.chat Greetings testers! It's meeting time again! If anyone has any other items for the agenda, please reply to this email and suggest them! Thanks. == Proposed Agenda Topics == 1. Previous meeting follow-up 2. Fedora 39 status 3. Rawhide update test gating 4. Toolbox criterion proposal 5. Test Day / community event status 6. Open floor -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net ___ test-announce mailing list -- test-annou...@lists.fedoraproject.org To unsubscribe send an email to test-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/test-annou...@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Fedora Copr builders updated to Fedora 38
Pavel Raiskup wrote: > I'm not strongly against anything; but rather than weaker policy for > everything I slightly prefer keeping the _stricter default policy_ with > _disabled gpgcheck for EL6_ (we should phase epel-6 out entirely anyway > since it's long time EOL, but we still keep it for the distro upgrade > team(s)). This is up to the community to decide, let us know in our > issue tracker if you are concerned. Considering that Fedora buildroots always get killed off within days of the EOL, I do not see why you are keeping epel-6 buildroots active 2½ years (!) after its EOL. 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Using AI/Machine Learning with rpmautospec?
Yes, but all rpm distros could use of it and in theory it could be extended to non-rpms as well if you used the right abstraction layer. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F39 Change Proposal: Build JDKs once, repack everywhere (System-Wide Change)
Hello! I have updated contingency plan: https://fedoraproject.org/wiki/Changes/BuildJdkOncePackEverywhere#Contingency_Plan / https://fedoraproject.org/w/index.php?title=Changes%2FBuildJdkOncePackEverywhere=revision=679828=679493 Sorry for not writing this out of the box. It was written so many times I consider it as "widely known" but obviously I was wrong. Sorry for that. J. On Tue, 30 May 2023 at 20:38, Aoife Moloney wrote: > > This document represents a proposed Change. As part of the Changes > process, proposals are publicly announced in order to receive > community feedback. This proposal will only be implemented if approved > by the Fedora Engineering Steering Committee. > > == Summary == > > This is the last step in > https://fedoraproject.org/wiki/MoveFedoraJDKsToBecomePortableJDKs > effort. Jdks in fedora are already static, and we repack portable > tarball into rpms. Currently, the portbale tarball is built for each > Fedora and Epel version. Goal here is to build each jdk > (8,11,17,21,latest (20)) only once, in oldest live Fedora xor Epel and > repack in all live fedoras. > > == Owner == > > * Name: [[User:jvanek| Jiri Vanek]] > * Email: jva...@redhat.com > > > == Detailed Description == > > As described in > https://fedoraproject.org/wiki/MoveFedoraJDKsToBecomePortableJDKs ; > during last year, packaging of JDKs had changed dramatically. As > described in same wiki page, and individual sub changes and devel > threads, with primary reason this - to lower maintenance and still > keep fedora java friendly. > > * In first system wide change, we had changed JDKs to build properly > as standalone, portable jdk - the wey JDK is supposed to be built. I > repeat, we spent ten years by patching JDK to become properly dynamic > against system libs, and all patches went usptream, but it become > fight which can not be win > > * as a second step we introduced portable rpms, which do not have any > system integration, only builds JDK and pack final tarball in RPM for > free use. > > * In third step - without any noise, just verified with fesco - > https://pagure.io/fesco/issue/2907 - we stopped building JDK in fully > integrated rpms. Instead of this, normal RPMS BUildRequire portable > rpms and just unpack it, and repack it. > > Now last step is ahead - to build portable LTS JDKs 8,11,17 and 21 in > oldest live Fedora, and repack everywhere. java-latest-openjdk, which > contains latest STS jdk - currently 20, soon briefly 21 and a bit > alter 22... Should be built in latest live EPEL - epel8 now. We have > verified, that such repacked JDKs work fine. > > == Feedback == > > > == Benefit to Fedora == > > java maintainers will finally some free time... No kidding - > maintenance and *certification* of so much supported JDKs on so much > Fedora versions is brutal. By building once, and repack, we will > regain cycles to continue support Fedora with all LTS and one STS > javas. > > If we fail to build once and repack everywhere, java maintainers will > most likely need to lower the number of JDKs in fedora to system one > only. > > == Scope == > * Proposal owners: Technically all jdks (except 8, where some more > tuning is needed, and epels for java-latest) are prepared, as they > have portable version, and rpms just reapck it. Except tuning up the > jdk8 and epel for latest, scope owners are done. > > > * Other developers: There will be needed significant support from RCM > and maybe senior fedora leadership to help to finish the build in > oldest and enable to repack everywhere Aoife Moloney > > Product Owner > > Community Platform Engineering Team > > Red Hat EMEA > > Communications House > > Cork Road > > Waterford > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Using AI/Machine Learning with rpmautospec?
On Fri, 09 Jun 2023 21:22:44 - Reon Beon via devel wrote: > It it atomaticly add/update the spec file when more files are added > in the right places in the spec file? So, are you suggesting that a neural network be trained on all existing spec files in fedora, and then used to automatically correct new spec files? That seems like a lot of work, and is the theoretical concept even sound? That is, is there too much variation in spec files, even correct spec files, because of the underlying variation in material being packaged, to allow a neural network to be trained and function correctly? Sounds like a great summer intern project, or the seed for a PhD thesis. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
pghmcfc pushed to rpms/perl-MCE-Shared (rawhide). "Update to 1.885 (..more)"
Notification time stamped 2023-06-10 12:07:00 UTC
From 0086367d91a3127e2121e700e53d6412c2b08cba Mon Sep 17 00:00:00 2001
From: Paul Howarth
Date: Jun 10 2023 12:06:19 +
Subject: Update to 1.885
- New upstream release 1.885
- Fix typo in Queue dequeue_timed documentation
---
diff --git a/perl-MCE-Shared.spec b/perl-MCE-Shared.spec
index 111ec6a..bd0b895 100644
--- a/perl-MCE-Shared.spec
+++ b/perl-MCE-Shared.spec
@@ -1,5 +1,5 @@
Name: perl-MCE-Shared
-Version: 1.884
+Version: 1.885
Release: 1%{?dist}
Summary: MCE extension for sharing data, supporting threads and processes
License: GPL-1.0-or-later OR Artistic-1.0-Perl
@@ -92,6 +92,10 @@ make test
%{_mandir}/man3/MCE::Shared::Server.3*
%changelog
+* Fri Jun 9 2023 Paul Howarth - 1.885-1
+- Update to 1.885
+ - Fix typo in Queue dequeue_timed documentation
+
* Thu Jun 8 2023 Paul Howarth - 1.884-1
- Update to 1.884
- Add missing return statement(s) in Condvar and Queue
diff --git a/sources b/sources
index 722eff4..20ce474 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (MCE-Shared-1.884.tar.gz) =
b05a7d3a3b4de4b8693db123e35adcb360e312649c054e8bef94f1ad3cfb4c499fbe1228b4d6782a21323a37120a18ce46188ba5857f66f61e3f1be9ffe0fb5b
+SHA512 (MCE-Shared-1.885.tar.gz) =
d3bb6d94260987387c958ab4324e7d69d53b5e7895f6e925fcdc96aacf785d639fed3ce12294f2b7caea50757b03f9b04ec5c7f8e57ea4c2932d9a455e9c9a81
https://src.fedoraproject.org/rpms/perl-MCE-Shared/c/0086367d91a3127e2121e700e53d6412c2b08cba?branch=rawhide
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
[Test-Announce] Fedora 39 Rawhide 20230610.n.0 nightly compose nominated for testing
Announcing the creation of a new nightly release validation test event for Fedora 39 Rawhide 20230610.n.0. Please help run some tests for this nightly compose if you have time. For more information on nightly release validation testing, see: https://fedoraproject.org/wiki/QA:Release_validation_test_plan Notable package version changes: anaconda - 20230603.n.1: anaconda-39.16-2.fc39.src, 20230610.n.0: anaconda-39.18-1.fc39.src pungi - 20230603.n.1: pungi-4.3.8-3.fc39.src, 20230610.n.0: pungi-4.4.0-1.fc39.src Test coverage information for the current release can be seen at: https://openqa.fedoraproject.org/testcase_stats/39 You can see all results, find testing instructions and image download locations, and enter results on the Summary page: https://fedoraproject.org/wiki/Test_Results:Fedora_39_Rawhide_20230610.n.0_Summary The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora_39_Rawhide_20230610.n.0_Installation https://fedoraproject.org/wiki/Test_Results:Fedora_39_Rawhide_20230610.n.0_Base https://fedoraproject.org/wiki/Test_Results:Fedora_39_Rawhide_20230610.n.0_Server https://fedoraproject.org/wiki/Test_Results:Fedora_39_Rawhide_20230610.n.0_Cloud https://fedoraproject.org/wiki/Test_Results:Fedora_39_Rawhide_20230610.n.0_Desktop https://fedoraproject.org/wiki/Test_Results:Fedora_39_Rawhide_20230610.n.0_Security_Lab Thank you for testing! -- Mail generated by relvalconsumer: https://pagure.io/fedora-qa/relvalconsumer ___ test-announce mailing list -- test-annou...@lists.fedoraproject.org To unsubscribe send an email to test-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/test-annou...@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2213846] perl-MCE-1.887 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2213846 Fedora Update System changed: What|Removed |Added Status|MODIFIED|CLOSED Fixed In Version||perl-MCE-1.887-1.fc39 Resolution|--- |ERRATA Last Closed||2023-06-10 08:31:01 --- Comment #2 from Fedora Update System --- FEDORA-2023-219b536833 has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2213846 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202213846%23c2 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2213846] perl-MCE-1.887 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2213846 Fedora Update System changed: What|Removed |Added Status|NEW |MODIFIED --- Comment #1 from Fedora Update System --- FEDORA-2023-219b536833 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-219b536833 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2213846 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202213846%23c1 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
