Re: Retiring the pcre package from Fedora

[Paolo Bonzini]

On 7/24/22 15:42, Kalev Lember wrote:
On Sun, Jul 24, 2022 at 8:58 AM Paolo Bonzini > wrote:




Il sab 23 lug 2022, 19:12 Adam Williamson
mailto:adamw...@fedoraproject.org>> ha
scritto:

This of course begs a question: did qemu also have a non-static pcre
requirement at the time? But it seems not:

[adamw@xps13k qemu (f36 %)]$ git show 0835325:qemu.spec | grep pcre
BuildRequires: glibc-static pcre-static glib2-static zlib-static

so, I'm not sure why Daniel concluded this needs a BuildRequires on
pcre-static, but the obvious thing to do would be to ask him, I
guess.


I think it could have been a missing requires of glib2-static,
because glib does use PCRE and therefore has it in the linker flags
for a static build. I will check next time I am at a computer.


glib2 switched to pcre2 in rawhide recently. Can you check if qemu needs 
to be updated for that now so that it BuildRequires pcre2-static instead?


Yep, that works.  I still think that pcre2-static and 
sysprof-capture-devel belong in glib2's spec file though, but I 
committed that as a stopgap measure.


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

Re: Fedora 37 mass rebuild complete

[Sérgio Basto]

On Mon, 2022-07-25 at 21:55 -0500, Richard Shaw wrote:
> On Mon, Jul 25, 2022 at 4:47 PM Miro Hrončok 
> wrote:
> > On 25. 07. 22 23:38, Richard W.M. Jones wrote:
> > > On Mon, Jul 25, 2022 at 08:57:39AM -0700, Kevin Fenzi wrote:
> > >> Hi all,
> > >>
> > >> Per the Fedora 37 schedule[1] we started a mass rebuild for
> > Fedora
> > >> 37 on 2022/07/20. We did a mass rebuild for Fedora 37 for:
> > >>
> > >> https://pagure.io/releng/issues?status=Open=mass+rebuild
> > >>
> > >> The mass rebuild was done in a side tag (f37-rebuild) and moved
> > over to
> > >> f37. Failures can be seen
> > >>
> > https://kojipkgs.fedoraproject.org/mass-rebuild/f37-failures.html 
> > Things
> > >> still needing rebuilding
> > >>
> > https://kojipkgs.fedoraproject.org/mass-rebuild/f37-need-rebuild.html
> > > I could be being stupid here, but what's the difference between
> > > packages that failed to build and packages that need rebuilding?
> > 
> > Considering "need-rebuild" is a superset of "failures" (I've just
> > checked [1]) 
> > the 2 differences I can think of are:
> > 
> > 1) Only builds that manage to get past buildSRPMFromSCM are
> > associated to the 
> > particular package by Koji. Hence, packages that failed
> > buildSRPMFromSCM or 
> > when the Koji build was not even submitted (i.e. there was no spec
> > file, 
> > missing source, RPM parse error, noautobuild file, etc.) -- such
> > package swill 
> > onyl be listed in "need-rebuild" as there is no known associated
> > build failure 
> > with them.
> > 
> 
> 
> Exactly, almost all of the packages for me are not direct failures,
> but related to vtk not building (and probably cascades down from
> there but I stopped drilling down).


I already did one PR to fix the this (vtk) issue  

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


> A couple are due to libusb-devel being retired. I'm surprised there
> weren't bugs already filed for that. I would think detecting packages
> using retired dependencies would be somewhat trivial to discover.
> 
> Thanks,
> Richard
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines:
> https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure

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

[Bug 2110574] perl-HTTP-CookieJar-0.014 is available

[bugzilla]

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



--- Comment #3 from Upstream Release Monitoring 
 ---
the-new-hotness/release-monitoring.org's scratch build of
perl-HTTP-CookieJar-0.014-1.fc36.src.rpm for rawhide completed
http://koji.fedoraproject.org/koji/taskinfo?taskID=90028920


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

[Bug 2110771] rt-5.0.3 is available

[bugzilla]

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



--- Comment #2 from Upstream Release Monitoring 
 ---
the-new-hotness/release-monitoring.org's scratch build of
rt-5.0.3-1.fc36.src.rpm for rawhide failed
http://koji.fedoraproject.org/koji/taskinfo?taskID=90041064


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

[HEADS UP] wxGTK 3.2.0 in Rawhide

[Scott Talbert]

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


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


I've rebuilt these existing users in a side tag (f37-build-side-7):
- CubicSDR
- audacity
- wxmacmolplot

I see that erlang also snuck in as a user recently.  :)  @Peter, can you 
please rebuild erlang in side tag f37-build-side-7?  It should rebuild 
fine without any changes (I tested in copr).


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

[Bug 2110816] New: perl-File-Share-0.26 is available

[bugzilla]

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

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



Releases retrieved: 0.26
Upstream release that is considered latest: 0.26
Current version/release in rawhide: 0.25-24.fc37
URL: http://search.cpan.org/dist/File-Share

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


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


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


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


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


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

[Test-Announce] Fedora 37 Rawhide 20220725.n.1 nightly compose nominated for testing

[rawhide]

Announcing the creation of a new nightly release validation test event
for Fedora 37 Rawhide 20220725.n.1. 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 - 20220721.n.0: anaconda-37.11-1.fc37.src, 20220725.n.1: 
anaconda-37.11-2.fc37.src
python-blivet - 20220721.n.0: python-blivet-3.5.0-1.fc37.src, 20220725.n.1: 
python-blivet-3.5.0-2.fc37.src
pyparted - 20220721.n.0: pyparted-3.12.0-5.fc37.src, 20220725.n.1: 
pyparted-3.12.0-6.fc37.src
parted - 20220721.n.0: parted-3.5-3.fc37.src, 20220725.n.1: 
parted-3.5-4.fc37.src
pykickstart - 20220721.n.0: pykickstart-3.41-2.fc37.src, 20220725.n.1: 
pykickstart-3.41-3.fc37.src
lorax - 20220721.n.0: lorax-37.6-1.fc37.src, 20220725.n.1: lorax-37.7-2.fc37.src

Test coverage information for the current release can be seen at:
https://openqa.fedoraproject.org/testcase_stats/37

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_37_Rawhide_20220725.n.1_Summary

The individual test result pages are:

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

Re: Fedora 37 mass rebuild complete

[Miro Hrončok]

On 25. 07. 22 23:38, Richard W.M. Jones wrote:

On Mon, Jul 25, 2022 at 08:57:39AM -0700, Kevin Fenzi wrote:

Hi all,

Per the Fedora 37 schedule[1] we started a mass rebuild for Fedora
37 on 2022/07/20. We did a mass rebuild for Fedora 37 for:

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

The mass rebuild was done in a side tag (f37-rebuild) and moved over to
f37. Failures can be seen
https://kojipkgs.fedoraproject.org/mass-rebuild/f37-failures.html  Things
still needing rebuilding
https://kojipkgs.fedoraproject.org/mass-rebuild/f37-need-rebuild.html

I could be being stupid here, but what's the difference between
packages that failed to build and packages that need rebuilding?


Considering "need-rebuild" is a superset of "failures" (I've just checked [1]) 
the 2 differences I can think of are:


1) Only builds that manage to get past buildSRPMFromSCM are associated to the 
particular package by Koji. Hence, packages that failed buildSRPMFromSCM or 
when the Koji build was not even submitted (i.e. there was no spec file, 
missing source, RPM parse error, noautobuild file, etc.) -- such package swill 
onyl be listed in "need-rebuild" as there is no known associated build failure 
with them.


2) Immediately after I submitted a newer build of a package that was initially 
listed in "failures", it got removed form that list. Assuming my build would 
fail, it would probbaly only stayed in



Unfortunately, only failures from "failures" are reported in bugzilla [2], but 
I think they should be opened for all packages from "need-rebuild".



[1]
$ comm -23 <(grep -F 'href="http://koji.fedoraproject.org/koji/packageinfo?packageID=' 
f37-need-rebuild.html | sort | uniq) <(grep -F 'href="http://koji.fedoraproject.org/koji/packageinfo?packageID=' 
f37-failures.html | sort | uniq) | wc -l

1392
$ comm -13 ...snip... | wc -l
0

[2] https://pagure.io/releng/issue/8601

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

Re: Fedora 37 mass rebuild complete

[Richard W.M. Jones]

On Mon, Jul 25, 2022 at 08:57:39AM -0700, Kevin Fenzi wrote:
> Hi all,
> 
> Per the Fedora 37 schedule[1] we started a mass rebuild for Fedora
> 37 on 2022/07/20. We did a mass rebuild for Fedora 37 for:
> 
> https://pagure.io/releng/issues?status=Open=mass+rebuild
> 
> The mass rebuild was done in a side tag (f37-rebuild) and moved over to
> f37. Failures can be seen
> https://kojipkgs.fedoraproject.org/mass-rebuild/f37-failures.html Things
> still needing rebuilding
> https://kojipkgs.fedoraproject.org/mass-rebuild/f37-need-rebuild.html

I could be being stupid here, but what's the difference between
packages that failed to build and packages that need rebuilding?

Rich.

> 21713 builds have been tagged into f37, there is currently 1144 failed
> builds that need to be addressed by the package maintainers. FTBFS bugs
> will be filed shortly. Please be sure to let releng know if you see any
> bugs in the reporting. You can contact releng in #fedora-releng on
> libera.chat, by dropping an email to our list[2], joining
> #releng:fedoraproject.org on Matrix, or filing an issue in pagure[3]
> 
> Regards,
> Fedora Release Engineering
> 
> [1] https://fedorapeople.org/groups/schedule/f-N/f-N-key-tasks.html
> [2] 
> https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/
> [3] https://pagure.io/releng/
> 



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

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


-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
http://libguestfs.org/virt-builder.1.html
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2110771] rt-5.0.3 is available

[bugzilla]

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



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


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

[Bug 2110771] New: rt-5.0.3 is available

[bugzilla]

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

Bug ID: 2110771
   Summary: rt-5.0.3 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: rt
  Keywords: FutureFeature, Triaged
  Assignee: rc040...@freenet.de
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: j...@tib.bs, perl-devel@lists.fedoraproject.org,
rc040...@freenet.de
  Target Milestone: ---
Classification: Fedora



Releases retrieved: 4.4.6, 5.0.3
Upstream release that is considered latest: 5.0.3
Current version/release in rawhide: 5.0.2-4.fc37
URL: http://bestpractical.com/request-tracker/

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


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


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


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


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/rt


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

[Bug 2110574] perl-HTTP-CookieJar-0.014 is available

[bugzilla]

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

Yanko Kaneti  changed:

   What|Removed |Added

   Doc Type|--- |If docs needed, set a value
 Resolution|--- |RAWHIDE
 Status|NEW |CLOSED
Last Closed||2022-07-25 17:09:54



--- Comment #2 from Yanko Kaneti  ---
https://koji.fedoraproject.org/koji/buildinfo?buildID=2031291


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

[Bug 2110574] New: perl-HTTP-CookieJar-0.014 is available

[bugzilla]

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

Bug ID: 2110574
   Summary: perl-HTTP-CookieJar-0.014 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-HTTP-CookieJar
  Keywords: FutureFeature, Triaged
  Assignee: yan...@declera.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: perl-devel@lists.fedoraproject.org, yan...@declera.com
  Target Milestone: ---
Classification: Fedora



Releases retrieved: 0.014
Upstream release that is considered latest: 0.014
Current version/release in rawhide: 0.012-4.fc37
URL: http://search.cpan.org/dist/HTTP-CookieJar/

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


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


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


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


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


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

[Bug 2110575] New: perl-HTTP-Tiny-0.082 is available

[bugzilla]

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

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



Releases retrieved: 0.082
Upstream release that is considered latest: 0.082
Current version/release in rawhide: 0.080-488.fc37
URL: http://search.cpan.org/dist/HTTP-Tiny/

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


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


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


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


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


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

[Bug 2110574] perl-HTTP-CookieJar-0.014 is available

[bugzilla]

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



--- Comment #1 from Upstream Release Monitoring 
 ---
Scratch build failed. Details below:

BuilderException: Build started, but failure happened during post build
operations:
Command '['git', 'commit', '-a', '-m', 'Update to 0.014 (#2110574)']' returned
non-zero exit status 1.

StdOut:
On branch rawhide
Your branch is up to date with 'origin/rawhide'.

Untracked files:
  (use "git add ..." to include in what will be committed)
SRPMS/

nothing added to commit but untracked files present (use "git add" to track)


Traceback:
  File
"/usr/local/lib/python3.10/site-packages/hotness/use_cases/package_scratch_build_use_case.py",
line 56, in build
result = self.builder.build(request.package, request.opts)
  File "/usr/local/lib/python3.10/site-packages/hotness/builders/koji.py", line
226, in build
raise BuilderException(

If you think this issue is caused by some bug in the-new-hotness, please report
it on the-new-hotness issue tracker:
https://github.com/fedora-infra/the-new-hotness/issues


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

Fedora 37 mass rebuild complete

[Kevin Fenzi]

Hi all,

Per the Fedora 37 schedule[1] we started a mass rebuild for Fedora
37 on 2022/07/20. We did a mass rebuild for Fedora 37 for:

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

The mass rebuild was done in a side tag (f37-rebuild) and moved over to
f37. Failures can be seen
https://kojipkgs.fedoraproject.org/mass-rebuild/f37-failures.html Things
still needing rebuilding
https://kojipkgs.fedoraproject.org/mass-rebuild/f37-need-rebuild.html

21713 builds have been tagged into f37, there is currently 1144 failed
builds that need to be addressed by the package maintainers. FTBFS bugs
will be filed shortly. Please be sure to let releng know if you see any
bugs in the reporting. You can contact releng in #fedora-releng on
libera.chat, by dropping an email to our list[2], joining
#releng:fedoraproject.org on Matrix, or filing an issue in pagure[3]

Regards,
Fedora Release Engineering

[1] https://fedorapeople.org/groups/schedule/f-N/f-N-key-tasks.html
[2] https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/
[3] https://pagure.io/releng/



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

Fedora 37 mass rebuild complete

[Kevin Fenzi]

Hi all,

Per the Fedora 37 schedule[1] we started a mass rebuild for Fedora
37 on 2022/07/20. We did a mass rebuild for Fedora 37 for:

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

The mass rebuild was done in a side tag (f37-rebuild) and moved over to
f37. Failures can be seen
https://kojipkgs.fedoraproject.org/mass-rebuild/f37-failures.html Things
still needing rebuilding
https://kojipkgs.fedoraproject.org/mass-rebuild/f37-need-rebuild.html

21713 builds have been tagged into f37, there is currently 1144 failed
builds that need to be addressed by the package maintainers. FTBFS bugs
will be filed shortly. Please be sure to let releng know if you see any
bugs in the reporting. You can contact releng in #fedora-releng on
libera.chat, by dropping an email to our list[2], joining
#releng:fedoraproject.org on Matrix, or filing an issue in pagure[3]

Regards,
Fedora Release Engineering

[1] https://fedorapeople.org/groups/schedule/f-N/f-N-key-tasks.html
[2] https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/
[3] https://pagure.io/releng/



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

Re: repoquery-fu (was Re: Retiring the pcre package from Fedora)

[Fabio Valentini]

On Mon, Jul 25, 2022 at 1:50 AM Demi Marie Obenour
 wrote:
>
> Rust *already* has full dynamic linking support, and this is used
> on Android to save space and memory.  What Rust does not have is
> a stable ABI.  Therefore, when Rust code changes, all Rust code
> depending on it must be recompiled.  The same is true for Haskell
> with GHC.  To make this maintainable, the necessary recompiles must
> be automated, so that when a new version of e.g. hyper is pushed,
> all packages that use hyper are rebuilt automatically.

Google can do this for Android, because they control *the entire stack*.
We can't, because all published Rust crates that matter don't support
being built that way.
Before we talk about making something maintainable, it should be
*possible* in the first place.

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

[rpms/perl-Parallel-Iterator] PR #1: Tests

[Jitka Plesnikova]

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

Merged pull-request:

``
Tests
``

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

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

[Jens-Ulrik Petersen]

>From the 28.1 NEWS file: this seems to be a breaking change:

** The WHEN argument of 'make-obsolete' and related functions is mandatory.
> The use of those functions without a WHEN argument was marked obsolete
> back in Emacs 23.1.  The affected functions are: 'make-obsolete',
> 'define-obsolete-function-alias', 'make-obsolete-variable',
> 'define-obsolete-variable-alias'.
>

which if I am not wrong probably caused several of emacs-* packages to
FTBFS in the mass rebuild.
(Unfortunately the build.log's only refer to the line-number in the elisp
files: dunno if that can be improved?)

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

[rpms/perl-Parallel-Iterator] PR #1: Tests

[Jitka Plesnikova]

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

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

[Bug 2103762] perl-Sys-Virt-8.5.0 is available

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

 Resolution|--- |RAWHIDE
   Fixed In Version||perl-Sys-Virt-8.5.0-1.fc37
 Status|ASSIGNED|CLOSED
Last Closed||2022-07-25 14:15:26




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

Re: Retiring the pcre package from Fedora

[Sérgio Basto]

On Fri, 2022-07-22 at 14:52 +0200, Petr Pisar wrote:
> V Fri, Jul 22, 2022 at 02:24:00PM +0200, Lukas Javorsky napsal(a):
> > As from the pcre-8.45, the upstream stopped supporting this
> > library. The
> > recommended procedure is to switch onto the new pcre2 library that
> > has full
> > upstream support. [1]
> > 
> > As a result of this announcement, the older PCRE library in Fedora
> > will be
> > retired.
> > Without upstream support, we don't have enough capacity to keep up
> > with the
> > security and bugs-related issues, and thus we will support only the
> > new
> > PCRE2 library. [2]
> > 
> > The retirement procedure will happen in the upcoming weeks, so if
> > you would
> > like to take over the package let us know.
> > 
> > 
> > The list of affected packages:
> > 389-ds-base
> > 389-ds-base-libs
> > EMBOSS-libs
> [...]
> > perl
> 
> I'm not sure what "affected" means here, but e.g. perl has no direct
> dependency on pcre. Maybe your computation is not correct.
> 

only perl-re-engine-PCRE (maintained by: jplesnik, ppisar)


Depending on: pcre (141),
389-ds-base (maintained by: abbra, mreynolds, rmeggins, spichugi,
tbordaz, vashirov)
389-ds-base-2.2.2-1.fc37.src requires pcre-devel = 8.45-1.fc36.1
389-ds-base-2.2.2-1.fc37.x86_64 requires libpcre.so.1()(64bit)
389-ds-base-libs-2.2.2-1.fc37.x86_64 requires libpcre.so.1()(64bit)

ClanLib (maintained by: jwrdegoede)
ClanLib-2.3.7-25.fc36.src requires pcre-devel = 8.45-1.fc36.1
ClanLib-devel-2.3.7-25.fc36.i686 requires pcre-devel = 8.45-1.fc36.1
ClanLib-devel-2.3.7-25.fc36.x86_64 requires pcre-devel = 8.45-1.fc36.1

EMBOSS (maintained by: spot)
EMBOSS-6.6.0-20.fc36.src requires pcre-devel = 8.45-1.fc36.1
EMBOSS-libs-6.6.0-20.fc36.i686 requires libpcre.so.1
EMBOSS-libs-6.6.0-20.fc36.x86_64 requires libpcre.so.1()(64bit)
libeplplot-6.6.0-20.fc36.i686 requires libpcre.so.1
libeplplot-6.6.0-20.fc36.x86_64 requires libpcre.so.1()(64bit)

Falcon (maintained by: salimma)
Falcon-0.9.6.8-24.fc36.i686 requires libpcre.so.1
Falcon-0.9.6.8-24.fc36.src requires pkgconfig(libpcre) = 8.45
Falcon-0.9.6.8-24.fc36.x86_64 requires libpcre.so.1()(64bit)

GMT (maintained by: orion, scitech_sig)
GMT-6.4.0-1.fc37.i686 requires libpcre.so.1
GMT-6.4.0-1.fc37.src requires pcre-devel = 8.45-1.fc36.1
GMT-6.4.0-1.fc37.x86_64 requires libpcre.so.1()(64bit)

Io-language (maintained by: limb)
Io-language-20170906-7.fc37.i686 requires libpcre.so.1
Io-language-20170906-7.fc37.src requires pcre-devel = 8.45-1.fc36.1
Io-language-20170906-7.fc37.x86_64 requires libpcre.so.1()(64bit)

R (maintained by: spot)
R-4.1.3-1.fc37.src requires pcre-devel = 8.45-1.fc36.1
R-core-devel-4.1.3-1.fc37.i686 requires pcre-devel = 8.45-1.fc36.1
R-core-devel-4.1.3-1.fc37.x86_64 requires pcre-devel = 8.45-1.fc36.1

Thunar (maintained by: kevin, nonamedotc)
Thunar-4.16.11-1.fc37.i686 requires libpcre.so.1
Thunar-4.16.11-1.fc37.src requires pkgconfig(libpcre) = 8.45
Thunar-4.16.11-1.fc37.x86_64 requires libpcre.so.1()(64bit)

adanaxisgpl (maintained by: jwrdegoede)
adanaxisgpl-1.2.5-42.fc37.src requires pcre-devel = 8.45-1.fc36.1
adanaxisgpl-1.2.5-42.fc37.x86_64 requires libpcre.so.1()(64bit)

aide (maintained by: alakatos, rsroka, zfridric)
aide-0.16-19.fc36.src requires pcre-devel = 8.45-1.fc36.1
aide-0.16-19.fc36.x86_64 requires libpcre.so.1()(64bit)

aircrack-ng (maintained by: xvitaly)
aircrack-ng-1.7-1.fc37.i686 requires libpcre.so.1
aircrack-ng-1.7-1.fc37.src requires pcre-devel = 8.45-1.fc36.1
aircrack-ng-1.7-1.fc37.x86_64 requires libpcre.so.1()(64bit)

anope (maintained by: robert)
anope-2.0.10-5.fc37.src requires pcre-devel = 8.45-1.fc36.1
anope-pcre-2.0.10-5.fc37.x86_64 requires libpcre.so.1()(64bit)

apachetop (maintained by: robert)
apachetop-0.19.7-7.fc36.src requires pcre-devel = 8.45-1.fc36.1

bigloo (maintained by: jjames, salimma)
bigloo-4.4c-5.4.fc37.src requires pkgconfig(libpcre) = 8.45

blender (maintained by: design-sw, ignatenkobrain, kwizart, luya,
music, roma, s4504kr, slaanesh)
blender-1:3.2.1-2.fc37.src requires pkgconfig(libpcre) = 8.45

bti (maintained by: salimma)
bti-034-24.fc36.src requires pkgconfig(libpcre) = 8.45
bti-034-24.fc36.x86_64 requires libpcre.so.1()(64bit)

ccze (maintained by: dcavalca, epel-packagers-sig, salimma)
ccze-0.2.1-28.fc36.src requires pcre-devel = 8.45-1.fc36.1
ccze-0.2.1-28.fc36.x86_64 requires libpcre.so.1()(64bit)

cegui (maintained by: bruno, jwrdegoede, timn)
cegui-0.8.7-24.fc37.i686 requires libpcre.so.1
cegui-0.8.7-24.fc37.src requires pcre-devel = 8.45-1.fc36.1
cegui-0.8.7-24.fc37.x86_64 requires libpcre.so.1()(64bit)

cegui06 (maintained by: bruno, jwrdegoede)
cegui06-0.6.2-38.fc37.src requires pcre-devel = 8.45-1.fc36.1
cegui06-0.6.2-38.fc37.x86_64 requires libpcre.so.1()(64bit)

clamav (maintained by: gnat, janfrode, mstevens, nb, orion, pwouters,
robert, sergiomb, steve)
clamav-0.103.6-1.fc37.src requires pcre-devel = 8.45-1.fc36.1

clisp (maintained by: green, jjames)
clisp-2.49.93-23.20210628gitde01f0f.fc36.i686 requires libpcre.so.1

[Bug 2110225] perl-Devel-CheckOS-1.94 is available

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|NEW |CLOSED
 Resolution|--- |RAWHIDE
   Doc Type|--- |If docs needed, set a value
   Fixed In Version||perl-Devel-CheckOS-1.94-1.f
   ||c37
Last Closed||2022-07-25 13:20:57




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

Re: Retiring the pcre package from Fedora

[Ben Cotton]

On Sat, Jul 23, 2022 at 5:55 PM Kevin Kofler via devel
 wrote:
>
> We just need to accept that we need to maintain pcre as a compatibility
> library for the foreseeable future.

I'm sympathetic to your "we shouldn't block people from maintaining
things if they want to" argument, but I have to disagree here. There's
only so much time that the community can collectively devote to Fedora
and this is not a place I'd like us to spend it. If someone really
wants to maintain a package that upstream has moved on from, then good
for them. But it's better for us to help other upstreams that depend
on this old version to use the newer library, whether that's by direct
contribution or peer pressure.

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

Re: F37 proposal: z13 as the Baseline for IBM Z Hardware (Self-Contained Change proposal)

[Stephen Gallagher]

On Fri, Jul 22, 2022 at 4:02 AM Daniel P. Berrangé  wrote:
...
> Note, in terms of software compatibility with newer CPU baseline,
> this has already been widely tested given that RHEL-8 built with
> the z13 baseline and RHEL-9 built with z14 baseline.

> I do agree though that this feels like the kind of change that
> makes sense todo all in one go at a mass rebuild, rather than
> drip-feeding per-package.
>
> Given Fedora has lagged waay behind RHEL in its s390x baseline
> for years, I'm not seeing why there's a need to rush this in Fedora
> late in the F37 cycle, rather than co-ordinating it for the F38
> release to leverage a mass rebuild.


Just to add one more datapoint: we've been building all of the
packages in ELN with the z13 baseline for months now, so we do in fact
already know the impact / build failure risk.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Upstream Release Monitoring - bug report

[Michal Schorm]

Ah, It's a bit more tangled than I thought:

I've somehow got an impression that the upstream release monitoring is
not related to Fedora, but I expected the BZ bot should be.
So I've looked for a place to report issues other than
https://github.com/fedora-infra/anitya/issues, as I thought it is the
upstream (not Fedora related) part of the project. Only after
following the link I've seen it is a GitHub repo in the "fedora-infra"
namespace.

I've actually thought that the "monitoring status" option in the
src.fedoraproject.org does something different (pings you when
_anyone_ do a build or scratch-build of your package in KOJI - which
would be useful for watching who touches your pkg and how)

The Pagure documentation doesn't seem to know about that field:
https://docs.pagure.org/pagure/search.html?q=monitoring

So the 'Monitoring' value is likely what I am looking for, thanks ! :)

--

On Mon, Jul 25, 2022 at 1:46 PM Fabio Valentini  wrote:
> This sounds like it's trying to process and create patches for *the
> same version* again and again?
> If that is the case, you might want to file a bug with anitya /
> the-new-hotness, as that's certainly not its intended behaviour.

Right, will report.

--

Michal Schorm
Software Engineer
Core Services - Databases Team
Red Hat

--

On Mon, Jul 25, 2022 at 1:46 PM Fabio Valentini  wrote:
>
> On Mon, Jul 25, 2022 at 1:39 PM Michal Schorm  wrote:
> >
> > Hello,
> > I don't know where to go, so I'm trying here.
> >
> > Package 'mariadb-connector-c' [1] I maintain has upstream release
> > monitoring enabled [2].
> > The bot opened a BZ [3] for me to notify about a new upstream release
> > - as expected.
> >
> > It tried to come up with a patch and try to scratch-build the package
> > with the patch.
> > However it failed.
> > And now it tries again and again, failing every time. Littering the BZ
> > ticket with more and more comments with zero value. Spamming people in
> > CC every day or two.
> >
> > I want it to stop.
> >
> > Ideally, I would like the bot to stop trying making patches and doing
> > scratch builds on all my packages at all. It's a wasted effort (and
> > computing time; and KOJI resources).
> >
> > Is that possible?
> > How?
> >
> > --
> >
> > I logged into the https://release-monitoring.org/ , but there doesn't
> > seem to be any setting regarding that.
>
> release-monitoring.org only has a mapping from upstream projects to
> Fedora package names, but Fedora-specific settings live on
> src.fedoraproject.org.
> So, if you go to
> https://src.fedoraproject.org/rpms/mariadb-connector-c (you actually
> linked that page yourself), and are logged in:
>
> In the left-hand pane, there's a combobox where you can select "No
> monitoring", "Monitoring", and "Scratch builds".
> It's currently set to "Scratch builds", but if you know that those
> won't work, then change the setting to "Monitoring".
> That will at least cut down the number of notifications.
>
> > And now it tries again and again, failing every time.
>
> This sounds like it's trying to process and create patches for *the
> same version* again and again?
> If that is the case, you might want to file a bug with anitya /
> the-new-hotness, as that's certainly not its intended behaviour.
>
> Fabio
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it: 
> https://pagure.io/fedora-infrastructure
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Upstream Release Monitoring - bug report

[Fabio Valentini]

On Mon, Jul 25, 2022 at 1:39 PM Michal Schorm  wrote:
>
> Hello,
> I don't know where to go, so I'm trying here.
>
> Package 'mariadb-connector-c' [1] I maintain has upstream release
> monitoring enabled [2].
> The bot opened a BZ [3] for me to notify about a new upstream release
> - as expected.
>
> It tried to come up with a patch and try to scratch-build the package
> with the patch.
> However it failed.
> And now it tries again and again, failing every time. Littering the BZ
> ticket with more and more comments with zero value. Spamming people in
> CC every day or two.
>
> I want it to stop.
>
> Ideally, I would like the bot to stop trying making patches and doing
> scratch builds on all my packages at all. It's a wasted effort (and
> computing time; and KOJI resources).
>
> Is that possible?
> How?
>
> --
>
> I logged into the https://release-monitoring.org/ , but there doesn't
> seem to be any setting regarding that.

release-monitoring.org only has a mapping from upstream projects to
Fedora package names, but Fedora-specific settings live on
src.fedoraproject.org.
So, if you go to
https://src.fedoraproject.org/rpms/mariadb-connector-c (you actually
linked that page yourself), and are logged in:

In the left-hand pane, there's a combobox where you can select "No
monitoring", "Monitoring", and "Scratch builds".
It's currently set to "Scratch builds", but if you know that those
won't work, then change the setting to "Monitoring".
That will at least cut down the number of notifications.

> And now it tries again and again, failing every time.

This sounds like it's trying to process and create patches for *the
same version* again and again?
If that is the case, you might want to file a bug with anitya /
the-new-hotness, as that's certainly not its intended behaviour.

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

Re: Upstream Release Monitoring - bug report

[Artur Frenszek-Iwicki]

> I would like the bot to stop trying making patches and doing scratch builds 
> on all my packages at all.
> Is that possible? How?
Isn't that controlled in Pagure, via the "monitoring" dropdown on the repo page?
There's "no monitoring", "monitoring" and "monitoring with scratch builds" 
options.
The mariadb-connector-c package has the last option selected.

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

Upstream Release Monitoring - bug report

[Michal Schorm]

Hello,
I don't know where to go, so I'm trying here.

Package 'mariadb-connector-c' [1] I maintain has upstream release
monitoring enabled [2].
The bot opened a BZ [3] for me to notify about a new upstream release
- as expected.

It tried to come up with a patch and try to scratch-build the package
with the patch.
However it failed.
And now it tries again and again, failing every time. Littering the BZ
ticket with more and more comments with zero value. Spamming people in
CC every day or two.

I want it to stop.

Ideally, I would like the bot to stop trying making patches and doing
scratch builds on all my packages at all. It's a wasted effort (and
computing time; and KOJI resources).

Is that possible?
How?

--

I logged into the https://release-monitoring.org/ , but there doesn't
seem to be any setting regarding that.

--

In the meanwhile, I've found one more tiny bug:
(A) The link to Fedora wiki page about the upstream release monitoring
leads to an obsoleted page:
https://fedoraproject.org/wiki/Upstream_release_monitoring

--

[1] https://src.fedoraproject.org/rpms/mariadb-connector-c
[2] https://release-monitoring.org/project/16939/
[3] https://bugzilla.redhat.com/show_bug.cgi?id=2090416

--

Michal Schorm
Software Engineer
Core Services - Databases Team
Red Hat

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

[HEADS-UP] rust2rpm v22

[Fabio Valentini]

Hi all,

The Rust SIG has finished working on the next release of Rust
packaging tools, rust2rpm v22. The changes to the RPM macros
themselves are minor (and were actually already backported to the
Fedora packages for rust2rpm v21), but the changes to rust2rpm are
pretty big:

The headline item is probably the automatic stripping of dependencies
for "foreign" targets, which should make most manually maintained
patches for Rust crate packages in Fedora unnecessary. Additionally,
we've refactored the rust2rpm python module, so the core functionality
that's required for the rust-packaging RPM macros no longer depends on
any third-party python packages.

Please refer to the release notes for more details:
https://pagure.io/fedora-rust/rust2rpm/blob/main/f/NEWS

I've submitted updates for v22 to rawhide, f36, and f35, which should
be pushed *soon* (still waiting for the gating tests to pass):

https://bodhi.fedoraproject.org/updates/FEDORA-2022-60c698a60f
https://bodhi.fedoraproject.org/updates/FEDORA-2022-6dcc99ae76
https://bodhi.fedoraproject.org/updates/FEDORA-2022-04e23a1f12

Existing Rust packages should continue to build as usual, since the
RPM macros have not changed. If you encounter problems with
/usr/bin/rust2rpm, please either file a ticket in the upstream project
(https://pagure.io/fedora-rust/rust2rpm) or ping us in the "Fedora
Rust" channel on matrix if you're unsure whether something is a
feature or a bug. :)

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

Fedora rawhide compose report: 20220725.n.0 changes

[Fedora Rawhide Report]

OLD: Fedora-Rawhide-20220724.n.0
NEW: Fedora-Rawhide-20220725.n.0

= SUMMARY =
Added images:0
Dropped images:  1
Added packages:  0
Dropped packages:1
Upgraded packages:   90
Downgraded packages: 2

Size of added packages:  0 B
Size of dropped packages:28.21 KiB
Size of upgraded packages:   6.16 GiB
Size of downgraded packages: 1.61 MiB

Size change of upgraded packages:   31.09 MiB
Size change of downgraded packages: 70.57 KiB

= ADDED IMAGES =

= DROPPED IMAGES =
Image: Server raw-xz aarch64
Path: Server/aarch64/images/Fedora-Server-Rawhide-20220724.n.0.aarch64.raw.xz

= ADDED PACKAGES =

= DROPPED PACKAGES =
Package: rust-restson-0.6.0-5.fc36
Summary: Easy-to-use REST client with automatic serialization and 
deserialization
RPMs:rust-restson+default-devel rust-restson-devel
Size:28.21 KiB


= UPGRADED PACKAGES =
Package:  Io-language-20170906-7.fc37
Old package:  Io-language-20170906-5.fc37
Summary:  Io is a small, prototype-based programming language
RPMs: Io-language Io-language-devel Io-language-extras 
Io-language-graphics-and-sound Io-language-mysql Io-language-postgresql
Size: 6.47 MiB
Size change:  469.03 KiB
Changelog:
  * Wed Jul 20 2022 Fedora Release Engineering  - 
20170906-6
  - Rebuilt for https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild

  * Sun Jul 24 2022 Robert-Andr?? Mauchin  - 20170906-7
  - Rebuilt for Ode soname bump


Package:  alienarena-7.71.2-6.fc37
Old package:  alienarena-7.71.2-4.fc36
Summary:  Multiplayer retro sci-fi deathmatch game
RPMs: alienarena alienarena-data alienarena-server
Size: 766.62 MiB
Size change:  714.92 KiB
Changelog:
  * Wed Jul 20 2022 Fedora Release Engineering  - 
7.71.2-5
  - Rebuilt for https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild

  * Sun Jul 24 2022 Robert-Andr?? Mauchin  - 7.71.2-6
  - Rebuilt for Ode soname bump


Package:  cinnamon-5.4.7-1.fc37
Old package:  cinnamon-5.4.5-1.fc37
Summary:  Window management and application launching for GNOME
RPMs: cinnamon cinnamon-calendar-server cinnamon-devel-doc
Size: 9.23 MiB
Size change:  512.12 KiB
Changelog:
  * Wed Jul 20 2022 Fedora Release Engineering  - 
5.4.5-2
  - Rebuilt for https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild

  * Sun Jul 24 2022 Leigh Scott  - 5.4.7-1
  - Update to 5.4.7 release


Package:  cinnamon-settings-daemon-5.4.3-1.fc37
Old package:  cinnamon-settings-daemon-5.4.1-1.fc37
Summary:  The daemon sharing settings from CINNAMON to GTK+/KDE applications
RPMs: cinnamon-settings-daemon cinnamon-settings-daemon-devel
Size: 2.00 MiB
Size change:  105.28 KiB
Changelog:
  * Wed Jul 20 2022 Fedora Release Engineering  - 
5.4.1-2
  - Rebuilt for https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild

  * Sun Jul 24 2022 Leigh Scott  - 5.4.3-1
  - Update to 5.4.3 release


Package:  cinnamon-translations-5.4.2-1.fc37
Old package:  cinnamon-translations-5.4.0-1.fc37
Summary:  Translations for Cinnamon and Nemo
RPMs: cinnamon-translations
Size: 3.87 MiB
Size change:  152.05 KiB
Changelog:
  * Wed Jul 20 2022 Fedora Release Engineering  - 
5.4.0-2
  - Rebuilt for https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild

  * Sun Jul 24 2022 Leigh Scott  - 5.4.2-1
  - Update to 5.4.2 release


Package:  fossil-2.19-1.fc37
Old package:  fossil-2.18-2.fc37
Summary:  A distributed SCM with bug tracking and wiki
RPMs: fossil fossil-doc
Size: 13.49 MiB
Size change:  341.58 KiB
Changelog:
  * Sun Jul 24 2022 Sheng Mao  - 2.19-1
  - New upstream release 2.19


Package:  freewrl-4.3.0-13.20200221gite99ab4a.fc37
Old package:  freewrl-4.3.0-11.20200221gite99ab4a.fc36
Summary:  X3D / VRML visualization program
RPMs: freewrl freewrl-devel freewrl-java libEAI libEAI-devel
Size: 42.93 MiB
Size change:  24.11 MiB
Changelog:
  * Thu Jul 21 2022 Fedora Release Engineering  - 
4.3.0-12.20200221gite99ab4a
  - Rebuilt for https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild

  * Sun Jul 24 2022 Robert-Andr?? Mauchin  - 
4.3.0-13.20200221gite99ab4a
  - Rebuilt for Ode soname bump


Package:  gajim-1.4.7-1.fc37
Old package:  gajim-1.4.6-1.fc37
Summary:  Jabber client written in PyGTK
RPMs: gajim
Size: 7.04 MiB
Size change:  191.97 KiB
Changelog:
  * Thu Jul 21 2022 Fedora Release Engineering  - 
1.4.6-2
  - Rebuilt for https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild

  * Sun Jul 24 2022 Michael Kuhn  - 1.4.7-1
  - Update to 1.4.7


Package:  gap-pkg-datastructures-0.2.7-3.fc37
Old package:  gap-pkg-datastructures-0.2.7-1.fc37
Summary:  Standard data structures for GAP
RPMs: gap-pkg-datastructures gap-pkg-datastructures-doc
Size: 666.21 KiB
Size change:  58.18 KiB
Changelog:
  * Thu Jul 21 2022 Fedora Release Engineering  - 
0.2.7-2
  - Rebuilt for https://fedoraproject.org/wiki

Re: Retiring the pcre package from Fedora

[Petr Pisar]

V Mon, Jul 25, 2022 at 11:38:49AM +0200, Lukas Javorsky napsal(a):
> I'm still going to create a COPR build for every dependent package with
> change from "pcre" to "pcre2" requirement, so I can report each of the
> components, if it's able to just simply change to pcre2 or need to port.

If you find a package which builds after replacing BuildRequires, you should
rather report a bug.

Each package should explicitly configure enabled and disabled features instead
of automatically enabling and disabling features based on a presence of
developmental files in a build root. These automagically enabled features are
a source of nondeterminism (sponteaous build failures and feature flips)
triggered by changes in indirectly dependenent and unrelated packages.

-- Petr


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

Re: Retiring the pcre package from Fedora

[Lukas Javorsky]

Quite a lot of reading but thanks everyone for the emails.

Few observations I get from this email thread (correct me if I
misunderstood anything):

1) We don't have a unified process for how to do such a retirement/orphan
package workflow.

2) We don't have a deterministic unified tool/script for how to find all
packages that depend on the "want-to-be-orphaned" package. Looks like the
one that Fabio provides is quite good, it may be worth to document it
somewhere, so it can be used in future.

3) It looks like there are some packages that don't even know why they
require the pcre package. This may be worth investigating for the
maintainers, so the package doesn't require something that is not even used.

4) There are some folks that are willing to take over the maintenance of
the pcre package. I'm still going to create a COPR build for every
dependent package with change from "pcre" to "pcre2" requirement, so I can
report each of the components, if it's able to just simply change to pcre2
or need to port.
However, after that, I will pass the component to the people that want
to maintain it. I can see that Vitaly (FAS = xvitaly) is willing, feel free
to message me if there is anybody else that wants to help him.

For the packages that are going to port their code to pcre2, you can do it
in the upcoming release, so you don't need to rush, we
appreciate you're doing it.

Thank you all for all of the insightful information and help.
Lukas

On Mon, Jul 25, 2022 at 10:23 AM Mamoru TASAKA 
wrote:

> Kalev Lember wrote on 2022/07/25 0:45:
> > On Sun, Jul 24, 2022 at 4:45 PM Mamoru TASAKA  >
> > wrote:
> >
> >> Kalev Lember wrote on 2022/07/24 22:42:
> >>> glib2 switched to pcre2 in rawhide recently. Can you check if qemu
> needs
> >> to
> >>> be updated for that now so that it BuildRequires pcre2-static instead?
> >>>
> >>>
> >>
> https://src.fedoraproject.org/rpms/glib2/c/34b203d5499b579c68b4f923a29fd417efdd9637?branch=rawhide
> >>>
> >>
> >> Ah... maybe due to this?
> >>
> >> A.
> >> On mass-rebuid, rubygem-glib2 (which is a wrapper to glib2 for ruby
> >> language) sees
> >> test failure with regards to "g_regex_match_all" - note that this is
> s390x
> >> only.
> >>
> >> https://koji.fedoraproject.org/koji/taskinfo?taskID=89955927
> >>
> >> B.
> >> I got lxrandr behavior regression on rawhide:
> >> https://bugzilla.redhat.com/show_bug.cgi?id=2109187
> >>
> >> - what lxrandr does here is lxrander gets the result of "xrandr" and
> >> passes it to "g_regex_match".
> >> On F-36 actually "g_regex_match" matches but (while I have not tried
> >> yet)
> >> what bug reporter says must be that "g_regex_match" now fails with
> >> rawhide glib2 (this is happening on x86_64).
> >>
> >> I will recheck this tomorrow.
> >>
> >
> > Those both sound a lot like regressions in g_regex_match() to me. If you
> > have time, any chance you could create smaller reproducers and file
> issues
> > for these upstream at https://gitlab.gnome.org/GNOME/glib ?
>
> For issue A: reported (with smallest reproducer):
> https://gitlab.gnome.org/GNOME/glib/-/issues/2699
>
> Now I will recheck issue B (maybe tomorrow...)
>
> Mamoru
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
>


-- 
S pozdravom/ Best regards

Lukáš Javorský

Software Engineer, Core service - Databases

Red Hat 

Purkyňova 115 (TPB-C)

612 00 Brno - Královo Pole

ljavo...@redhat.com

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

[Bug 2106292] CVE-2022-1955 perl-SNMP_Session: lack of adequate security controls may lead to information disclosure

[bugzilla]

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

TEJ RATHI  changed:

   What|Removed |Added

 Status|NEW |CLOSED
 Resolution|--- |NOTABUG
Last Closed||2022-07-25 07:54:30




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

Re: Retiring the pcre package from Fedora

[Mamoru TASAKA]

Kalev Lember wrote on 2022/07/25 0:45:

On Sun, Jul 24, 2022 at 4:45 PM Mamoru TASAKA 
wrote:


Kalev Lember wrote on 2022/07/24 22:42:

glib2 switched to pcre2 in rawhide recently. Can you check if qemu needs

to

be updated for that now so that it BuildRequires pcre2-static instead?



https://src.fedoraproject.org/rpms/glib2/c/34b203d5499b579c68b4f923a29fd417efdd9637?branch=rawhide




Ah... maybe due to this?

A.
On mass-rebuid, rubygem-glib2 (which is a wrapper to glib2 for ruby
language) sees
test failure with regards to "g_regex_match_all" - note that this is s390x
only.

https://koji.fedoraproject.org/koji/taskinfo?taskID=89955927

B.
I got lxrandr behavior regression on rawhide:
https://bugzilla.redhat.com/show_bug.cgi?id=2109187

- what lxrandr does here is lxrander gets the result of "xrandr" and
passes it to "g_regex_match".
On F-36 actually "g_regex_match" matches but (while I have not tried
yet)
what bug reporter says must be that "g_regex_match" now fails with
rawhide glib2 (this is happening on x86_64).

I will recheck this tomorrow.



Those both sound a lot like regressions in g_regex_match() to me. If you
have time, any chance you could create smaller reproducers and file issues
for these upstream at https://gitlab.gnome.org/GNOME/glib ?
 
For issue A: reported (with smallest reproducer): https://gitlab.gnome.org/GNOME/glib/-/issues/2699


Now I will recheck issue B (maybe tomorrow...)

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

[Bug 2106292] CVE-2022-1955 perl-SNMP_Session: lack of adequate security controls may lead to information disclosure

[bugzilla]

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



--- Comment #3 from TEJ RATHI  ---
Agree, This one is not related to perl-snmp-session. It is something related to
oxen-io/session-android package which does not shipped in RHEL and not even
Fedora. I'm closing out this bug.


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