[Bug 2162651] perl-Sub-Quote-2.006008 is available

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

   Fixed In Version||perl-Sub-Quote-2.006008-1.f
   ||c38
 Status|ASSIGNED|CLOSED
 Resolution|--- |RAWHIDE
Last Closed||2023-01-25 06:38:50




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2162651
___
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

[rpms/perl-Sub-Quote] PR #1: 2.006008 bump; Package tests

[Jitka Plesnikova]

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

Merged pull-request:

``
2.006008 bump; Package tests
``

https://src.fedoraproject.org/rpms/perl-Sub-Quote/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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2162841] Please, add perl-DateTime-Event-Recurrence to EPEL9

[bugzilla]

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



--- Comment #5 from David  ---
I grabbed the rpm's and installed them:

perl-DateTime-Event-Recurrence-0.19-19.el9
perl-DateTime-Set-0.3900-20.el9
perl-Set-Infinite-0.65-37.el9

Issues solved and the scheduling software now runs perfectly.

Thanks for the quick response.


Cheers,

David


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2162841
___
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

Re: Fedora 38 mass rebuild is finished

[Jeff Law]

On 1/24/23 15:52, Gary Buhrmaster wrote:



Had I seen cstdint I like to think that I would have
tried a rebuild with gcc 13 earlier to see what
(if any) upstream(s) needed some encouragement
for support gcc 13.
I actually did stuff like this in the past -- build all of Fedora with 
the new compiler as early as possible and then proceeded to fix as many 
of these trivial things as I could.


It was mostly done to keep the noise down in the tester so that the vast 
majority of the failures were actually compiler issues the team needed 
to address and to find deeper issues earlier in the cycle.


I've since moved on from Red Hat and don't even worry about any of the 
significant Fedora platforms anymore (I'm in risc-v land).  The mass 
rebuild testing I did was looking for something completely different, 
hence I didn't get through analysis of generic build failures as I was 
focused on a specific issue.


jeff
___
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 2162841] Please, add perl-DateTime-Event-Recurrence to EPEL9

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #4 from Fedora Update System  ---
FEDORA-EPEL-2023-5477508cfa has been pushed to the Fedora EPEL 9 testing
repository.

You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-5477508cfa

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2162841
___
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 2160110] perl-Sys-Statistics-Linux missing in EPEL-9

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Resolution|--- |ERRATA
   Fixed In Version||perl-Sys-Statistics-Linux-0
   ||.66-30.el9
 Status|ON_QA   |CLOSED
Last Closed||2023-01-25 00:49:03



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


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2160110
___
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 2158290] Please branch and build perl-File-KeePass for EPEL 9

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Resolution|--- |ERRATA
   Fixed In Version||perl-File-KeePass-2.03-30.e
   ||l9
 Status|ON_QA   |CLOSED
Last Closed||2023-01-25 00:48:58



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


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2158290
___
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

Re: Fedora 38 mass rebuild is finished

[Gary Buhrmaster]

On Tue, Jan 24, 2023 at 7:29 AM Jeff Law  wrote:

> On 1/24/23 00:16, Jakub Jelinek wrote:
> > See
> > https://gcc.gnu.org/gcc-13/porting_to.html#header-dep-changes
> > Some libstdc++ headers included  in older versions
> > as an implementation detail but no longer do.
> >
> > Including stdint.h will introduce ::uint32_t type among others,
> > but not std::uint32_t, if you use the latter, you need to
> > include .
> I've got a partial list of packages affected by the ongoing header
> cleanups in libstdc++:

I am in favor of header cleanups, and moving forward
with new(er) gcc versions, but I wonder that if in the
future the Fedora gcc change proposal can reference
the porting changes rather than referring only to the
main gcc docs as an additional heads up (in this case,
I skimmed the gcc 13 changes page, but you had to
follow yet another link for porting issues to see the
library header changes (and I did not go looking
there, my bad)).

While it may take me only a minute to recognize
the issue when I see the compile failure for a
missing header ("and there they go again..."),
writing PRs for upstreams and getting those fixes
into their release cycle may take somewhat longer
(and I prefer not to carry local patches in packages
when possible).

Had I seen cstdint I like to think that I would have
tried a rebuild with gcc 13 earlier to see what
(if any) upstream(s) needed some encouragement
for support gcc 13.

Thanks for the consideration.


___
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: Bootstrapping package with circular dependencies in koji

[Kevin Fenzi]

On Tue, Jan 24, 2023 at 03:36:41PM -0500, Neal Gompa wrote:
> On Tue, Jan 24, 2023 at 3:00 PM Kevin Fenzi  wrote:
> >
> > On Tue, Jan 24, 2023 at 07:54:29PM +0100, Jaroslav Skarvada wrote:
> > >
> > > I initially thought about:
> > > release bump
> > > $ koji edit-tag SIDETAG -x %_with_bootstrap=1
> > > build
> > > handle circular dep
> > > $ koji edit-tag SIDETAG -r %_with_bootstrap
> > > build
> > >
> > > But I haven't tried it yet because I didn't want to break anything :)
> > > Is this the correct way to do it?
> >
> > That should work, (as long as you bump the release for the second build
> > as koji will not let you rebuild the same n-v-r)
> > but I am not sure anyone has tried it.
> >
> 
> The NVR will automatically change when you flip between modes, since
> it changes the DistTag.

Ah indeed. 

So you should only need 1 initial commit. 

kevin


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

Retiring Bottles in favor of Flatpak provided by upstream

[Sandro]

Hi,

Development of Bottles is moving fast and we have been struggling to 
keep up with upstream releases, especially since the introduction of 
Rust components.


Upstream has approached the maintainers [1,2] and asked us to retire the 
package in favor of the Flatpak packages provided by upstream.


I'm planning to move forward with retiring Bottles in the coming days. I 
will add a comment in all open bug reports, letting users know they 
should switch to the Flatpak release.


Bottles in F36 and F37 will not receive any further updates unless there 
are security related issues surfacing.


[1] https://github.com/bottlesdevs/Bottles/issues/2345
[2] https://bugzilla.redhat.com/show_bug.cgi?id=2160007

Cheers,

Sandro
--
Sandro
FAS: gui1ty
IRC: Penguinpee
Elsewhere: [Pp]enguinpee
___
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 2164242] perl-Text-BibTeX-0.89 is available

[bugzilla]

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



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

GenericError: File upload failed:
cli-build/1674596402.536418.iBSNaYxa/perl-Text-BibTeX-0.89-1.fc36.src.rpm
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
198, in build
output["build_id"] = self._scratch_build(session, package.name, srpm)
  File "/usr/local/lib/python3.10/site-packages/hotness/builders/koji.py", line
451, in _scratch_build
session.uploadWrapper(source, serverdir)
  File "/usr/lib/python3.10/site-packages/koji/__init__.py", line 3083, in
uploadWrapper
self.fastUpload(localfile, path, name, callback, blocksize, overwrite,
volume=volume)
  File "/usr/lib/python3.10/site-packages/koji/__init__.py", line 3018, in
fastUpload
raise GenericError("File upload failed: %s/%s" % (path, name))

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=2164242
___
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 2164242] New: perl-Text-BibTeX-0.89 is available

[bugzilla]

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

Bug ID: 2164242
   Summary: perl-Text-BibTeX-0.89 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Text-BibTeX
  Keywords: FutureFeature, Triaged
  Assignee: c...@m.fsf.org
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: c...@m.fsf.org, perl-devel@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



Releases retrieved: 0.89
Upstream release that is considered latest: 0.89
Current version/release in rawhide: 0.88-13.fc38
URL: http://search.cpan.org/dist/Text-BibTeX

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://docs.fedoraproject.org/en-US/package-maintainers/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/5429/


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


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2164242
___
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

Re: Bootstrapping package with circular dependencies in koji

[Björn Persson]

Jaroslav Skarvada wrote:
> Thanks for the info, we will try it. It would be great to have it
> documented somewhere in the guidelines

Yes it would. This looks like a good place:
https://docs.fedoraproject.org/en-US/packaging-guidelines/#bootstrapping

"koji edit-tag --help" calls it "Set tag extra option". I would not
have guessed that an "extra option" would transform into an RPM macro,
nor that a "_with_" prefix would need to be added.

Björn Persson


pgpCIAUkIr_UN.pgp
Description: OpenPGP digital signatur
___
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: Bootstrapping package with circular dependencies in koji

[Jaroslav Skarvada]

On Tue, Jan 24, 2023 at 9:37 PM Neal Gompa  wrote:
>
> On Tue, Jan 24, 2023 at 3:00 PM Kevin Fenzi  wrote:
> >
> > On Tue, Jan 24, 2023 at 07:54:29PM +0100, Jaroslav Skarvada wrote:
> > >
> > > I initially thought about:
> > > release bump
> > > $ koji edit-tag SIDETAG -x %_with_bootstrap=1
> > > build
> > > handle circular dep
> > > $ koji edit-tag SIDETAG -r %_with_bootstrap
> > > build
> > >
> > > But I haven't tried it yet because I didn't want to break anything :)
> > > Is this the correct way to do it?
> >
> > That should work, (as long as you bump the release for the second build
> > as koji will not let you rebuild the same n-v-r)
> > but I am not sure anyone has tried it.
> >
>
> The NVR will automatically change when you flip between modes, since
> it changes the DistTag.
>
Thanks for the info, we will try it. It would be great to have it
documented somewhere in the guidelines

thanks & regards

Jaroslav
___
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: Bootstrapping package with circular dependencies in koji

[Neal Gompa]

On Tue, Jan 24, 2023 at 3:00 PM Kevin Fenzi  wrote:
>
> On Tue, Jan 24, 2023 at 07:54:29PM +0100, Jaroslav Skarvada wrote:
> >
> > I initially thought about:
> > release bump
> > $ koji edit-tag SIDETAG -x %_with_bootstrap=1
> > build
> > handle circular dep
> > $ koji edit-tag SIDETAG -r %_with_bootstrap
> > build
> >
> > But I haven't tried it yet because I didn't want to break anything :)
> > Is this the correct way to do it?
>
> That should work, (as long as you bump the release for the second build
> as koji will not let you rebuild the same n-v-r)
> but I am not sure anyone has tried it.
>

The NVR will automatically change when you flip between modes, since
it changes the DistTag.



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

Re: Fedora 38 mass rebuild is finished

[Jakub Jelinek]

On Tue, Jan 24, 2023 at 02:01:39PM -0600, Richard Shaw wrote:
> On Tue, Jan 24, 2023 at 7:20 AM Richard Shaw  wrote:
> 
> > hobbes1069 (9):
> > cqrlog - Fails for some weird lazbuild issue I don't understand
> > flnet - Spec conditional oops. Fixed.
> > flrig - Needed cstdint. Fixed
> > freecad - Needs cstdint. Working on it.
> > gmsh - Needed cstdint. Fixed.
> > openCOLLADA - error: possibly dangling reference to a temporary. Don't
> > know how to fix this one.
> > opencascade - error: declaration of 'tbb::task&
> > tbb::internal::task_prefix::task()' changes meaning of 'task'
> > openexr - Needed cstdint. Fixed.
> > spnavcfg - https://github.com/FreeSpacenav/spnavcfg/issues/30
> >
> 
> I think I've gotten everything situated except openCOLLADA.

See https://gcc.gnu.org/PR107532 and
https://gcc.gnu.org/pipermail/gcc-patches/2023-January/thread.html#610188
It is a new warning, which has some false positives and some further work
is being done on that, but whether openCOLLADA triggers a false positive
or has a real bug is something that somebody needs to analyze.
E.g. -fsanitize=address should diagnose similar use after scope bugs
at runtime.
Of course, packages which use -Werror need to be prepared to deal with new
warnings at any time.

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

Re: Fedora 38 mass rebuild is finished

[Richard Shaw]

On Tue, Jan 24, 2023 at 7:20 AM Richard Shaw  wrote:

> hobbes1069 (9):
> cqrlog - Fails for some weird lazbuild issue I don't understand
> flnet - Spec conditional oops. Fixed.
> flrig - Needed cstdint. Fixed
> freecad - Needs cstdint. Working on it.
> gmsh - Needed cstdint. Fixed.
> openCOLLADA - error: possibly dangling reference to a temporary. Don't
> know how to fix this one.
> opencascade - error: declaration of 'tbb::task&
> tbb::internal::task_prefix::task()' changes meaning of 'task'
> openexr - Needed cstdint. Fixed.
> spnavcfg - https://github.com/FreeSpacenav/spnavcfg/issues/30
>

I think I've gotten everything situated except openCOLLADA.

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

Re: Bootstrapping package with circular dependencies in koji

[Kevin Fenzi]

On Tue, Jan 24, 2023 at 07:54:29PM +0100, Jaroslav Skarvada wrote:
> 
> I initially thought about:
> release bump
> $ koji edit-tag SIDETAG -x %_with_bootstrap=1
> build
> handle circular dep
> $ koji edit-tag SIDETAG -r %_with_bootstrap
> build
> 
> But I haven't tried it yet because I didn't want to break anything :)
> Is this the correct way to do it?

That should work, (as long as you bump the release for the second build
as koji will not let you rebuild the same n-v-r)
but I am not sure anyone has tried it. 

The "old" way to do it, is as you assumed, to just modify the spec to
enable the bootstrap path, build and then change back. 

The sidetag way would save you a commit, so that seems better to me, but
up to you. 

kevin


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

[rpms/perl-Sub-Quote] PR #1: 2.006008 bump; Package tests

[Jitka Plesnikova]

jplesnik opened a new pull-request against the project: `perl-Sub-Quote` that 
you are following:
``
2.006008 bump; Package tests
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Sub-Quote/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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Most OCaml packages have broken deps now

[Richard W.M. Jones]

FYI debuginfo generation failed on several packages.  I've had to
disable it on a few to get around this.  For example:

https://koji.fedoraproject.org/koji/taskinfo?taskID=96625872
https://kojipkgs.fedoraproject.org//work/tasks/5943/96625943/build.log

I'm not clear exactly why this is happening.  Since it didn't happen
in the mass rebuild just like a few days ago, it must be some very
recent change in the build chain, yet I didn't change anything
significant in the OCaml package.  The only thing I can think of is
the new version of ocaml-findlib.

Rich.

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

Re: Bootstrapping package with circular dependencies in koji

[Jaroslav Skarvada]

On Tue, Jan 24, 2023 at 7:42 PM Neal Gompa  wrote:
>
> On Tue, Jan 24, 2023 at 1:39 PM Jaroslav Skarvada  wrote:
> >
> > Hi,
> >
> > I need to bootstrap package which has bootstrap support written
> > according to the [1]. I am able to bootstrap it locally (rpmbuild,
> > mock, ...) with the "--with bootstrap" or "-D '_with_bootstrap 1'". Is
> > there support for it in koji? E.g. something like:
> > koji build SIDE-TAG PACKAGE --bootstrap? Or do I have to manually do:
> > 1. patch:
> > - %bcond_with bootstrap
> > + %bcond_without bootstrap
> > 2. koji build SIDE-TAG SCM
> > 3. update the circular dep
> > 4. unpatch:
> > - %bcond_without bootstrap
> > + %bcond_with bootstrap
> > 5. release bump
> > 6. koji build SIDE-TAG SCM
> >
> > Or is there some better way?
> >
> > thanks & regards
> >
> > Jaroslav
> >
> > [1] https://docs.fedoraproject.org/en-US/packaging-guidelines/#bootstrapping
>
> You might be able to set macros in your build tags to switch back and
> forth between bootstrap mode. I don't recall exactly how this is done
> from the koji CLI though...
>

I initially thought about:
release bump
$ koji edit-tag SIDETAG -x %_with_bootstrap=1
build
handle circular dep
$ koji edit-tag SIDETAG -r %_with_bootstrap
build

But I haven't tried it yet because I didn't want to break anything :)
Is this the correct way to do it?
___
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: Late F38 proposal: Packaging 22+ (Self-Contained Change proposal)

[Miro Hrončok]

On 24. 01. 23 18:57, Neal Gompa wrote:

Also, isn't this basically going to break the pythondistdeps
generator, since it was switched to use packaging a while ago?


Break? No. It will only handle some invalid requirements or provided version as 
errors. The affected packages are listed in the proposal.


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

Re: Bootstrapping package with circular dependencies in koji

[Neal Gompa]

On Tue, Jan 24, 2023 at 1:39 PM Jaroslav Skarvada  wrote:
>
> Hi,
>
> I need to bootstrap package which has bootstrap support written
> according to the [1]. I am able to bootstrap it locally (rpmbuild,
> mock, ...) with the "--with bootstrap" or "-D '_with_bootstrap 1'". Is
> there support for it in koji? E.g. something like:
> koji build SIDE-TAG PACKAGE --bootstrap? Or do I have to manually do:
> 1. patch:
> - %bcond_with bootstrap
> + %bcond_without bootstrap
> 2. koji build SIDE-TAG SCM
> 3. update the circular dep
> 4. unpatch:
> - %bcond_without bootstrap
> + %bcond_with bootstrap
> 5. release bump
> 6. koji build SIDE-TAG SCM
>
> Or is there some better way?
>
> thanks & regards
>
> Jaroslav
>
> [1] https://docs.fedoraproject.org/en-US/packaging-guidelines/#bootstrapping

You might be able to set macros in your build tags to switch back and
forth between bootstrap mode. I don't recall exactly how this is done
from the koji CLI though...



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

Bootstrapping package with circular dependencies in koji

[Jaroslav Skarvada]

Hi,

I need to bootstrap package which has bootstrap support written
according to the [1]. I am able to bootstrap it locally (rpmbuild,
mock, ...) with the "--with bootstrap" or "-D '_with_bootstrap 1'". Is
there support for it in koji? E.g. something like:
koji build SIDE-TAG PACKAGE --bootstrap? Or do I have to manually do:
1. patch:
- %bcond_with bootstrap
+ %bcond_without bootstrap
2. koji build SIDE-TAG SCM
3. update the circular dep
4. unpatch:
- %bcond_without bootstrap
+ %bcond_with bootstrap
5. release bump
6. koji build SIDE-TAG SCM

Or is there some better way?

thanks & regards

Jaroslav

[1] https://docs.fedoraproject.org/en-US/packaging-guidelines/#bootstrapping
___
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 38 mass rebuild is finished

[Mattia Verga via devel]

Il 24/01/23 08:16, Jakub Jelinek ha scritto:
> On Tue, Jan 24, 2023 at 10:00:47AM +0300, Vascom wrote:
>> I have some packages failed.
>> One of them libtins. Problem is that:
>>
>> error: 'uint32_t' is not a member of 'std';
>>
>> Is it normal? Is it GCC 13 change?
> See
> https://gcc.gnu.org/gcc-13/porting_to.html#header-dep-changes
> Some libstdc++ headers included  in older versions
> as an implementation detail but no longer do.
>
> Including stdint.h will introduce ::uint32_t type among others,
> but not std::uint32_t, if you use the latter, you need to
> include .
>
>   Jakub

I think rawtherapee is FTB for this as well:

/builddir/build/BUILD/rawtherapee-5.9/rtengine/dcraw.h:187:13: error:
'uint32_t' does not name a type

and

/builddir/build/BUILD/rawtherapee-5.9/rtengine/dcraw.h:24:1: note:
'uint32_t' is defined in header ''; did you forget to '#include
'?

Should I patch dcraw.h to have '#include '?

Mattia

___
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 2164150] CVE-2023-24038 perl-HTML-StripScripts-Parser: perl-HTML-StripScripts: Handler for style attribute is vulnerable to ReDoS [fedora-all]

[bugzilla]

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

Guilherme de Almeida Suckevicz  changed:

   What|Removed |Added

 Blocks||2164147 (CVE-2023-24038)





Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=2164147
[Bug 2164147] CVE-2023-24038 perl-HTML-StripScripts: Handler for style
attribute is vulnerable to ReDoS
-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2164150
___
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 2164149] CVE-2023-24038 perl-HTML-StripScripts: Handler for style attribute is vulnerable to ReDoS [epel-all]

[bugzilla]

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

Guilherme de Almeida Suckevicz  changed:

   What|Removed |Added

 Blocks||2164147 (CVE-2023-24038)





Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=2164147
[Bug 2164147] CVE-2023-24038 perl-HTML-StripScripts: Handler for style
attribute is vulnerable to ReDoS
-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2164149
___
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 2164149] New: CVE-2023-24038 perl-HTML-StripScripts: Handler for style attribute is vulnerable to ReDoS [epel-all]

[bugzilla]

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

Bug ID: 2164149
   Summary: CVE-2023-24038 perl-HTML-StripScripts: Handler for
style attribute is vulnerable to ReDoS [epel-all]
   Product: Fedora EPEL
   Version: epel8
Status: NEW
 Component: perl-HTML-StripScripts
  Keywords: Security, SecurityTracking
  Severity: medium
  Priority: medium
  Assignee: xav...@bachelot.org
  Reporter: gsuck...@redhat.com
QA Contact: extras...@fedoraproject.org
CC: perl-devel@lists.fedoraproject.org,
xav...@bachelot.org
  Target Milestone: ---
Classification: Fedora




More information about this security flaw is available in the following bug:

http://bugzilla.redhat.com/show_bug.cgi?id=2164147

Disclaimer: Community trackers are created by Red Hat Product Security team on
a best effort basis. Package maintainers are required to ascertain if the flaw
indeed affects their package, before starting the update process.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2164149
___
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 2164148] CVE-2023-24038 perl-HTML-StripScripts: Handler for style attribute is vulnerable to ReDoS [fedora-all]

[bugzilla]

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



--- Comment #1 from Guilherme de Almeida Suckevicz  ---
Use the following template to for the 'fedpkg update' request to submit an
update for this issue as it contains the top-level parent bug(s) as well as
this tracking bug.  This will ensure that all associated bugs get updated
when new packages are pushed to stable.

=

# bugfix, security, enhancement, newpackage (required)
type=security

# low, medium, high, urgent (required)
severity=medium

# testing, stable
request=testing

# Bug numbers: 1234,9876
bugs=2164147,2164148

# Description of your update
notes=Security fix for [PUT CVEs HERE]

# Enable request automation based on the stable/unstable karma thresholds
autokarma=True
stable_karma=3
unstable_karma=-3

# Automatically close bugs when this marked as stable
close_bugs=True

# Suggest that users restart after update
suggest_reboot=False

==

Additionally, you may opt to use the bodhi web interface to submit updates:

https://bodhi.fedoraproject.org/updates/new


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2164148
___
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 2164151] CVE-2023-24038 perl-HTML-StripScripts-Parser: perl-HTML-StripScripts: Handler for style attribute is vulnerable to ReDoS [epel-all]

[bugzilla]

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



--- Comment #1 from Guilherme de Almeida Suckevicz  ---
Use the following template to for the 'fedpkg update' request to submit an
update for this issue as it contains the top-level parent bug(s) as well as
this tracking bug.  This will ensure that all associated bugs get updated
when new packages are pushed to stable.

=

# bugfix, security, enhancement, newpackage (required)
type=security

# low, medium, high, urgent (required)
severity=medium

# testing, stable
request=testing

# Bug numbers: 1234,9876
bugs=2164147,2164151

# Description of your update
notes=Security fix for [PUT CVEs HERE]

# Enable request automation based on the stable/unstable karma thresholds
autokarma=True
stable_karma=3
unstable_karma=-3

# Automatically close bugs when this marked as stable
close_bugs=True

# Suggest that users restart after update
suggest_reboot=False

==

Additionally, you may opt to use the bodhi web interface to submit updates:

https://bodhi.fedoraproject.org/updates/new


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2164151
___
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 2164149] CVE-2023-24038 perl-HTML-StripScripts: Handler for style attribute is vulnerable to ReDoS [epel-all]

[bugzilla]

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



--- Comment #1 from Guilherme de Almeida Suckevicz  ---
Use the following template to for the 'fedpkg update' request to submit an
update for this issue as it contains the top-level parent bug(s) as well as
this tracking bug.  This will ensure that all associated bugs get updated
when new packages are pushed to stable.

=

# bugfix, security, enhancement, newpackage (required)
type=security

# low, medium, high, urgent (required)
severity=medium

# testing, stable
request=testing

# Bug numbers: 1234,9876
bugs=2164147,2164149

# Description of your update
notes=Security fix for [PUT CVEs HERE]

# Enable request automation based on the stable/unstable karma thresholds
autokarma=True
stable_karma=3
unstable_karma=-3

# Automatically close bugs when this marked as stable
close_bugs=True

# Suggest that users restart after update
suggest_reboot=False

==

Additionally, you may opt to use the bodhi web interface to submit updates:

https://bodhi.fedoraproject.org/updates/new


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2164149
___
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 2164151] New: CVE-2023-24038 perl-HTML-StripScripts-Parser: perl-HTML-StripScripts: Handler for style attribute is vulnerable to ReDoS [epel-all]

[bugzilla]

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

Bug ID: 2164151
   Summary: CVE-2023-24038 perl-HTML-StripScripts-Parser:
perl-HTML-StripScripts: Handler for style attribute is
vulnerable to ReDoS [epel-all]
   Product: Fedora EPEL
   Version: epel8
Status: NEW
 Component: perl-HTML-StripScripts-Parser
  Keywords: Security, SecurityTracking
  Severity: medium
  Priority: medium
  Assignee: xav...@bachelot.org
  Reporter: gsuck...@redhat.com
QA Contact: extras...@fedoraproject.org
CC: perl-devel@lists.fedoraproject.org,
xav...@bachelot.org
  Target Milestone: ---
Classification: Fedora




More information about this security flaw is available in the following bug:

http://bugzilla.redhat.com/show_bug.cgi?id=2164147

Disclaimer: Community trackers are created by Red Hat Product Security team on
a best effort basis. Package maintainers are required to ascertain if the flaw
indeed affects their package, before starting the update process.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2164151
___
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 2164150] CVE-2023-24038 perl-HTML-StripScripts-Parser: perl-HTML-StripScripts: Handler for style attribute is vulnerable to ReDoS [fedora-all]

[bugzilla]

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



--- Comment #1 from Guilherme de Almeida Suckevicz  ---
Use the following template to for the 'fedpkg update' request to submit an
update for this issue as it contains the top-level parent bug(s) as well as
this tracking bug.  This will ensure that all associated bugs get updated
when new packages are pushed to stable.

=

# bugfix, security, enhancement, newpackage (required)
type=security

# low, medium, high, urgent (required)
severity=medium

# testing, stable
request=testing

# Bug numbers: 1234,9876
bugs=2164147,2164150

# Description of your update
notes=Security fix for [PUT CVEs HERE]

# Enable request automation based on the stable/unstable karma thresholds
autokarma=True
stable_karma=3
unstable_karma=-3

# Automatically close bugs when this marked as stable
close_bugs=True

# Suggest that users restart after update
suggest_reboot=False

==

Additionally, you may opt to use the bodhi web interface to submit updates:

https://bodhi.fedoraproject.org/updates/new


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2164150
___
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 2164151] CVE-2023-24038 perl-HTML-StripScripts-Parser: perl-HTML-StripScripts: Handler for style attribute is vulnerable to ReDoS [epel-all]

[bugzilla]

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

Guilherme de Almeida Suckevicz  changed:

   What|Removed |Added

 Blocks||2164147 (CVE-2023-24038)





Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=2164147
[Bug 2164147] CVE-2023-24038 perl-HTML-StripScripts: Handler for style
attribute is vulnerable to ReDoS
-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2164151
___
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 2164150] New: CVE-2023-24038 perl-HTML-StripScripts-Parser: perl-HTML-StripScripts: Handler for style attribute is vulnerable to ReDoS [fedora-all]

[bugzilla]

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

Bug ID: 2164150
   Summary: CVE-2023-24038 perl-HTML-StripScripts-Parser:
perl-HTML-StripScripts: Handler for style attribute is
vulnerable to ReDoS [fedora-all]
   Product: Fedora
   Version: 37
Status: NEW
 Component: perl-HTML-StripScripts-Parser
  Keywords: Security, SecurityTracking
  Severity: medium
  Priority: medium
  Assignee: xav...@bachelot.org
  Reporter: gsuck...@redhat.com
QA Contact: extras...@fedoraproject.org
CC: perl-devel@lists.fedoraproject.org,
xav...@bachelot.org
  Target Milestone: ---
Classification: Fedora




More information about this security flaw is available in the following bug:

http://bugzilla.redhat.com/show_bug.cgi?id=2164147

Disclaimer: Community trackers are created by Red Hat Product Security team on
a best effort basis. Package maintainers are required to ascertain if the flaw
indeed affects their package, before starting the update process.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2164150
___
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 2164148] CVE-2023-24038 perl-HTML-StripScripts: Handler for style attribute is vulnerable to ReDoS [fedora-all]

[bugzilla]

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

Guilherme de Almeida Suckevicz  changed:

   What|Removed |Added

 Blocks||2164147 (CVE-2023-24038)





Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=2164147
[Bug 2164147] CVE-2023-24038 perl-HTML-StripScripts: Handler for style
attribute is vulnerable to ReDoS
-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2164148
___
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 2164148] New: CVE-2023-24038 perl-HTML-StripScripts: Handler for style attribute is vulnerable to ReDoS [fedora-all]

[bugzilla]

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

Bug ID: 2164148
   Summary: CVE-2023-24038 perl-HTML-StripScripts: Handler for
style attribute is vulnerable to ReDoS [fedora-all]
   Product: Fedora
   Version: 37
Status: NEW
 Component: perl-HTML-StripScripts
  Keywords: Security, SecurityTracking
  Severity: medium
  Priority: medium
  Assignee: xav...@bachelot.org
  Reporter: gsuck...@redhat.com
QA Contact: extras...@fedoraproject.org
CC: perl-devel@lists.fedoraproject.org,
xav...@bachelot.org
  Target Milestone: ---
Classification: Fedora




More information about this security flaw is available in the following bug:

http://bugzilla.redhat.com/show_bug.cgi?id=2164147

Disclaimer: Community trackers are created by Red Hat Product Security team on
a best effort basis. Package maintainers are required to ascertain if the flaw
indeed affects their package, before starting the update process.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2164148
___
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

Re: F38 proposal: FPC repackaging (Self-Contained Change proposal)

[Mattia Verga via devel]

Il 24/01/23 18:02, Artur Frenszek-Iwicki ha scritto:
> fpc has a Requires: on the units package, so it should always be installed.
>
> The build failures for packages using FPC, as far as I can see, are all 
> packages
> using Lazarus. As far as I can tell, this is because Lazarus seems to quite 
> tightly
> depend on specific FPC versions, and historically, whenever we updated/rebuilt
> FPC, we also rebuilt Lazarus. This time I completely forgot to do this.
>
> I may be wrong here, but I'm like 99% sure that, since Lazarus was eventually 
> rebuilt
> during the Mass Rebuild, once lazarus-2.2.4-2.fc38 lands in the rawhide 
> buildroot,
> it should be possible to resubmit any failed packages as-is and they'll work 
> this time.
>
You're probably right, I now see that fpc-units- was installed in
the buildroot on the failed builds. I'll try to resubmit the builds and
see what happens.

Thank you.

Mattia

___
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

Late F38 proposal: Packaging 22+ (Self-Contained Change proposal)

[Ben Cotton]

NOTE: As explained by the owners in the Feedback section below, this
proposal was submitted after the deadline because the impact of the
package update proved to be broader than anticipated.

https://fedoraproject.org/wiki/Changes/Packaging_22%2B

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 ==
Update to a new upstream release of python-packaging contains a
breaking change. Since version 22+ upstream removed support for
[https://github.com/pypa/packaging/pull/407 LegacySpecifier and
LegacyVersion] some packages will break. This is a breaking change and
projects are encouraged to use versions adherent to
[https://peps.python.org/pep-0440/ PEP 440].

Note: Currently, we plan to update to 23.0, but this can be updated
even further. The change proposal explicitly mentions version 22+
because that version removed support for LegacyVersions and legacy
version specifiers.

== Owner ==
* Name: [[User:thrnciar| Tomáš Hrnčiar]]
* Email: thrnc...@redhat.com
* Name: [[User:mhroncok| Miro Hrončok]]
* Email: mhron...@redhat.com


== Detailed Description ==
 >>> # before 22.0
 >>> packaging.version.parse("This is a completely random string")
 

 >>> # after 22.0
 >>> packaging.version.parse("This is a completely random string")
 Traceback (most recent call last):
   File "", line 1, in 
   File "[...]/.venv/lib/python3.10/site-packages/packaging/version.py",
line 52, in parse
 return Version(version)
   File "[...]/.venv/lib/python3.10/site-packages/packaging/version.py",
line 197, in __init__
 raise InvalidVersion(f"Invalid version: '{version}'")
 packaging.version.InvalidVersion: Invalid version: 'This is a
completely random string'

This "feature" has been deprecated for nearly two years now.

PyPI has not permitted uploading packages with invalid versions for
even more years. The latest versions of pip should be
rejecting/erroring out on wheels with such versions as well. The
stricter metadata validation helps pip's dependency resolver's logic,
along with helping the broader ecology avoid needing to deal with
outside-of-standard tooling/behaviours.

Possible failures caused by upgraded python-packaging:

* pinned version of python-packaging
**cekit - https://bugzilla.redhat.com/show_bug.cgi?id=2162433
**python-limits -
https://src.fedoraproject.org/rpms/python-limits/pull-request/5

* tests containing unsupported versions need to be adjusted
**copr-backend - https://bugzilla.redhat.com/show_bug.cgi?id=2162436

* some packages provide incompatible versions and
python-rpm-generators are unable to parse them. See PRs links below
for inspiration on how to fix them.
**obs-service-set_version
**pcs
**pyodbc
**python-btchip
**python-dipy
**python-dropbox
**python-haversion -
https://src.fedoraproject.org/rpms/python-haversion/pull-request/1
**python-httplib2 - uses pyparsing in tests but does not BuildRequire
it directly
**python-lacrosse -
https://src.fedoraproject.org/rpms/python-lacrosse/pull-request/1
**python-pdir2 - the sed in `%prep` needs to be adjusted not to create
invalid `>=4.2.*` requirements
**python-pvc
**python-pytest-httpx

See also https://discuss.python.org/t/22782/19 for the exact errors of
most of the listed packages.

* unknown
**python-google-cloud-bigquery - package does not build in rawhide

=== How to deal with failures in Python RPM dependency generators ===

packaging is used in the Python RPM dependency generators (for
`python3dist()` and `python3.11dist()` Provides, Requires and
BuildRequires).

When the packaged software has now invalid versions or comparators,
you might need to fix the package.

Example problem:

 packaging.version.InvalidVersion: Invalid version: 'main'

See if the version of the Python package isn't failing to be
determined automatically and provide the missing information, see
https://src.fedoraproject.org/rpms/python-haversion/pull-request/1 or
https://src.fedoraproject.org/rpms/python-lacrosse/pull-request/1 and
https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/#_version_warning

Example problem:

  packaging.requirements.InvalidRequirement: Expected end or semicolon
(after version specifier)
 typing-extensions>=4.2.*
 \~\~\~\~\~^

(Backslashes added to the example as a naïve attempt to escape the
dashes form this wiki, ignore them).

Adjust the requirement not to use `.*` in versions when `<`, `<=`,
`>`, or `>=` is used, see https://discuss.python.org/t/22782

== Feedback ==
We are aware that we missed the Change proposal submission deadline,
originally we planned to ship this as a regular package update. While
doing an impact check we identified ~20 affected packages and we
decided to write this Change proposal for better transparency. We
believe there is enough time to complete this Change in time for the

Re: Late F38 proposal: Packaging 22+ (Self-Contained Change proposal)

[Neal Gompa]

On Tue, Jan 24, 2023 at 12:50 PM Ben Cotton  wrote:
>
> NOTE: As explained by the owners in the Feedback section below, this
> proposal was submitted after the deadline because the impact of the
> package update proved to be broader than anticipated.
>
> https://fedoraproject.org/wiki/Changes/Packaging_22%2B
>
> 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 ==
> Update to a new upstream release of python-packaging contains a
> breaking change. Since version 22+ upstream removed support for
> [https://github.com/pypa/packaging/pull/407 LegacySpecifier and
> LegacyVersion] some packages will break. This is a breaking change and
> projects are encouraged to use versions adherent to
> [https://peps.python.org/pep-0440/ PEP 440].
>
> Note: Currently, we plan to update to 23.0, but this can be updated
> even further. The change proposal explicitly mentions version 22+
> because that version removed support for LegacyVersions and legacy
> version specifiers.
>

Can the title of this Change be changed? It's not particularly clear
what this is from the title.

Also, isn't this basically going to break the pythondistdeps
generator, since it was switched to use packaging a while ago?



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

Late F38 proposal: Packaging 22+ (Self-Contained Change proposal)

[Ben Cotton]

NOTE: As explained by the owners in the Feedback section below, this
proposal was submitted after the deadline because the impact of the
package update proved to be broader than anticipated.

https://fedoraproject.org/wiki/Changes/Packaging_22%2B

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 ==
Update to a new upstream release of python-packaging contains a
breaking change. Since version 22+ upstream removed support for
[https://github.com/pypa/packaging/pull/407 LegacySpecifier and
LegacyVersion] some packages will break. This is a breaking change and
projects are encouraged to use versions adherent to
[https://peps.python.org/pep-0440/ PEP 440].

Note: Currently, we plan to update to 23.0, but this can be updated
even further. The change proposal explicitly mentions version 22+
because that version removed support for LegacyVersions and legacy
version specifiers.

== Owner ==
* Name: [[User:thrnciar| Tomáš Hrnčiar]]
* Email: thrnc...@redhat.com
* Name: [[User:mhroncok| Miro Hrončok]]
* Email: mhron...@redhat.com


== Detailed Description ==
 >>> # before 22.0
 >>> packaging.version.parse("This is a completely random string")
 

 >>> # after 22.0
 >>> packaging.version.parse("This is a completely random string")
 Traceback (most recent call last):
   File "", line 1, in 
   File "[...]/.venv/lib/python3.10/site-packages/packaging/version.py",
line 52, in parse
 return Version(version)
   File "[...]/.venv/lib/python3.10/site-packages/packaging/version.py",
line 197, in __init__
 raise InvalidVersion(f"Invalid version: '{version}'")
 packaging.version.InvalidVersion: Invalid version: 'This is a
completely random string'

This "feature" has been deprecated for nearly two years now.

PyPI has not permitted uploading packages with invalid versions for
even more years. The latest versions of pip should be
rejecting/erroring out on wheels with such versions as well. The
stricter metadata validation helps pip's dependency resolver's logic,
along with helping the broader ecology avoid needing to deal with
outside-of-standard tooling/behaviours.

Possible failures caused by upgraded python-packaging:

* pinned version of python-packaging
**cekit - https://bugzilla.redhat.com/show_bug.cgi?id=2162433
**python-limits -
https://src.fedoraproject.org/rpms/python-limits/pull-request/5

* tests containing unsupported versions need to be adjusted
**copr-backend - https://bugzilla.redhat.com/show_bug.cgi?id=2162436

* some packages provide incompatible versions and
python-rpm-generators are unable to parse them. See PRs links below
for inspiration on how to fix them.
**obs-service-set_version
**pcs
**pyodbc
**python-btchip
**python-dipy
**python-dropbox
**python-haversion -
https://src.fedoraproject.org/rpms/python-haversion/pull-request/1
**python-httplib2 - uses pyparsing in tests but does not BuildRequire
it directly
**python-lacrosse -
https://src.fedoraproject.org/rpms/python-lacrosse/pull-request/1
**python-pdir2 - the sed in `%prep` needs to be adjusted not to create
invalid `>=4.2.*` requirements
**python-pvc
**python-pytest-httpx

See also https://discuss.python.org/t/22782/19 for the exact errors of
most of the listed packages.

* unknown
**python-google-cloud-bigquery - package does not build in rawhide

=== How to deal with failures in Python RPM dependency generators ===

packaging is used in the Python RPM dependency generators (for
`python3dist()` and `python3.11dist()` Provides, Requires and
BuildRequires).

When the packaged software has now invalid versions or comparators,
you might need to fix the package.

Example problem:

 packaging.version.InvalidVersion: Invalid version: 'main'

See if the version of the Python package isn't failing to be
determined automatically and provide the missing information, see
https://src.fedoraproject.org/rpms/python-haversion/pull-request/1 or
https://src.fedoraproject.org/rpms/python-lacrosse/pull-request/1 and
https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/#_version_warning

Example problem:

  packaging.requirements.InvalidRequirement: Expected end or semicolon
(after version specifier)
 typing-extensions>=4.2.*
 \~\~\~\~\~^

(Backslashes added to the example as a naïve attempt to escape the
dashes form this wiki, ignore them).

Adjust the requirement not to use `.*` in versions when `<`, `<=`,
`>`, or `>=` is used, see https://discuss.python.org/t/22782

== Feedback ==
We are aware that we missed the Change proposal submission deadline,
originally we planned to ship this as a regular package update. While
doing an impact check we identified ~20 affected packages and we
decided to write this Change proposal for better transparency. We
believe there is enough time to complete this Change in time for the

Summary/Minutes from today's FESCo Meeting (2023-01-24)

[Zbigniew Jędrzejewski-Szmek]

Meeting summary
---
* init process  (zbyszek, 17:00:06)
  * Meeting is cancelled because of lack of quorum.  (zbyszek, 17:04:36)
  * ACTION: zbyszek will chair the next meeting.  (zbyszek, 17:04:45)

* Open Floor  (zbyszek, 17:04:49)

Meeting ended at 17:05:14 UTC.


Minutes: 
https://meetbot.fedoraproject.org/fedora-meeting/2023-01-24/fesco.2023-01-24-17.00.html
Minutes (text): 
https://meetbot.fedoraproject.org/fedora-meeting/2023-01-24/fesco.2023-01-24-17.00.txt
Log: 
https://meetbot.fedoraproject.org/fedora-meeting/2023-01-24/fesco.2023-01-24-17.00.log.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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Fedora 38 mass rebuild is finished

[Rafael Aquini]

On Mon, Jan 23, 2023 at 9:49 PM Kevin Fenzi  wrote:

> On Mon, Jan 23, 2023 at 08:11:03PM -0500, Rafael Aquini wrote:
> > FYI:
> >
> > memkind failure (aarch64) seems to be koji/mock related:
> >
> > This package was updated and sucessfully built in rawhide and f37 a week
> > ago (01/13)
> >
> > ---8<---
> >
> > EXCEPTION: [Error('Command failed: \n # /usr/bin/systemd-nspawn -q -M
> > b67a9ff69f3540e9bb559e45f9dafdf5 -D
> > /var/lib/mock/f38-build-40444675-4981555/root -a -u mockbuild
> > --capability=cap_ipc_lock
> > --bind=/tmp/mock-resolv._3nfqeom:/etc/resolv.conf
> > --bind=/dev/btrfs-control --bind=/dev/mapper/control
> > --bind=/dev/loop-control --bind=/dev/loop0 --bind=/dev/loop1
> > --bind=/dev/loop2 --bind=/dev/loop3 --bind=/dev/loop4
> > --bind=/dev/loop5 --bind=/dev/loop6 --bind=/dev/loop7
> > --bind=/dev/loop8 --bind=/dev/loop9 --bind=/dev/loop10
> > --bind=/dev/loop11 --console=pipe --setenv=TERM=vt100
> > --setenv=SHELL=/bin/bash --setenv=HOME=/builddir
> > --setenv=HOSTNAME=mock --setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin
> > --setenv=PROMPT_COMMAND=printf "\\033]0;\\007"
> > --setenv=PS1= \\s-\\v\\$  --setenv=LANG=C.UTF-8
> > --resolv-conf=off bash --login -c /usr/bin/rpmbuild -bb --noclean
> > --target aarch64 --nodeps /builddir/build/SPECS/memkind.spec\n', 1)]
> > Traceback (most recent call last):
> >   File "/usr/lib/python3.11/site-packages/mockbuild/trace_decorator.py",
> > line 93, in trace
> > result = func(*args, **kw)
> >
> > --->8---
>
> Very odd failure. :(
>
> It looks like it finished linking and then somehow systemd-nspawn
> crashed, but I don't see in the logs any reason why. :(
>
> I'd say try a scratch build and if that works, just resubmit it?
>
>
Kevin,

A local mock build helped identifying what seems to be the issue -- that
only happens with recent rawhide (as
I mentioned, I had the RPM successfully built last week, see [1]):

---8<---
libtool: link: gcc -shared  -fPIC -DPIC  src/.libs/hbwmalloc.o
src/.libs/heap_manager.o src/.libs/memkind.o src/.libs/memkind_arena.o
src/.libs/memkind_bitmask.o src/.libs/memkind_capacity.o
src/.libs/memkind_dax_kmem.o src/.libs/memkind_default.o
src/.libs/memkind_fixed.o src/.libs/memkind_gbtlb.o src/.libs/memkind_hbw.o
src/.libs/memkind_hugetlb.o src/.libs/memkind_interleave.o
src/.libs/memkind_local.o src/.libs/memkind_log.o
src/.libs/memkind_memtier.o src/.libs/memkind_mem_attributes.o
src/.libs/memkind_pmem.o src/.libs/memkind_regular.o
src/.libs/tbb_wrapper.o   -ldl -lrt -ldaxctl jemalloc/lib/libjemalloc_pic.a
-lm -lpthread -lnuma -Wl,-z,now
-specs=/usr/lib/rpm/redhat/redhat-hardened-ld -O2 -flto=auto -g
-grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1
-fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64
-mtune=generic -mno-omit-leaf-frame-pointer -fstack-protector -Wl,-z
-Wl,relro -Wl,--as-needed -Wl,-z -Wl,now
-specs=/usr/lib/rpm/redhat/redhat-hardened-ld
-specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1
-specs=/usr/lib/rpm/redhat/redhat-package-notes -Wl,-z -Wl,relro -Wl,-z
-Wl,now   -pthread -Wl,-soname -Wl,libmemkind.so.0 -o
.libs/libmemkind.so.0.0.1
gcc: fatal error: environment variable 'RPM_ARCH' not defined
compilation terminated.
make: *** [Makefile:2426: libmemkind.la] Error 1
--->8---

and this seem to be exactly what was reported at
https://bugzilla.redhat.com/show_bug.cgi?id=2142119

[1] https://koji.fedoraproject.org/koji/buildinfo?buildID=2110820

-- Rafael

>
>
___
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 38 mass rebuild is finished

[Jonathan Wakely]

On Tue, 24 Jan 2023 at 07:29, Jeff Law  wrote:
>
>
>
> On 1/24/23 00:16, Jakub Jelinek wrote:
> > On Tue, Jan 24, 2023 at 10:00:47AM +0300, Vascom wrote:
> >> I have some packages failed.
> >> One of them libtins. Problem is that:
> >>
> >> error: 'uint32_t' is not a member of 'std';
> >>
> >> Is it normal? Is it GCC 13 change?
> >
> > See
> > https://gcc.gnu.org/gcc-13/porting_to.html#header-dep-changes
> > Some libstdc++ headers included  in older versions
> > as an implementation detail but no longer do.
> >
> > Including stdint.h will introduce ::uint32_t type among others,
> > but not std::uint32_t, if you use the latter, you need to
> > include .
> I've got a partial list of packages affected by the ongoing header
> cleanups in libstdc++:
>
> intel-igc
> j4-dmenu-desktop
> julia
> jd
> jigdo
> mtxclient
> openclonk
> texlive-base
> tcpflow
> synergy
> R-svglite
> rstudio
> rssguard
> rpi-imager
> rocm-opencl
> rocksdb
> qucs
> parzip
> root
> openmsx
> openlierox
> openexr
> openexr2
> openms
> mongo-cxx-driver
> kakoune
>
>
> I'm sure there's more, I've probably looked at about 20% of the packaged
> I'd flagged as needing further analysis.  But that might help folks
> chase these things down.

The header cleanups will continue until morale improves!

The point of these changes is to speed up compilation. Removing
unnecessary headers means the compiler has less work to do, so koji
builds use less time and less power. The fixed package also becomes
more portable and more standard conforming. The  header isn't
expensive to compile, but what changed is actually that 
and  are no longer included in so many places, and those were
transitively including . Not including  where it
isn't needed removes thousands of lines of code. Most code seems to
remember to include  to use std::string, but everybody forgets
to include  for std::int32_t etc.

Looks like these have that issue and need to include :

widelands
warzone2100
uhd
usd
tcpflow
synergy
snapper
safeint
rstudio
rocksdb
rocm-opencl
prusa-slicer
plug
pingus
paraview
openms
openmsx

I didn't look at any packages starting with the letters A-N so there
are probably more.

Similarly, supertuxkart is missing  or .

pdns is missing 

openvdb failed but should work OK now as there's been an updated tbb.
___
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: F38 proposal: FPC repackaging (Self-Contained Change proposal)

[Artur Frenszek-Iwicki]

fpc has a Requires: on the units package, so it should always be installed.

The build failures for packages using FPC, as far as I can see, are all packages
using Lazarus. As far as I can tell, this is because Lazarus seems to quite 
tightly
depend on specific FPC versions, and historically, whenever we updated/rebuilt
FPC, we also rebuilt Lazarus. This time I completely forgot to do this.

I may be wrong here, but I'm like 99% sure that, since Lazarus was eventually 
rebuilt
during the Mass Rebuild, once lazarus-2.2.4-2.fc38 lands in the rawhide 
buildroot,
it should be possible to resubmit any failed packages as-is and they'll work 
this time.

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

Unannounced .so version bump in gtest 1.13.0

[Ben Beasley]

The recent update of gtest to 1.13.0 in Rawhide bumped the .so version. 
I reminded the maintainers of the Updates Policy for Rawhide and asked 
them to please announce and coordinate similar updates in the future[1].


The following packages depend on a specific .so version of gtest/gmock 
at runtime and already have FTI bugs: ceph, davix, gfal2, libcamera, 
mir, python-steps, and wlcs.


The list of packages that BuildRequire gtest/gmock is huge. I haven’t 
attempted to determine the full last of packages that could be impacted, 
or to explicitly (B)CC their maintainers on this message.


There is a higher than usual chance that packages that simply 
BuildRequire gtest/gmock will FTBFS, because gtest 1.13.0 drops support 
for C++ standard versions older than C++14. In *most* cases where a 
package’s build system enforces a specific older C++ version like C++11, 
it should be OK to patch that out and build with the compiler’s default 
C++ standard, or, more conservatively, enforce C++14 instead of C++11.


[1] https://bugzilla.redhat.com/show_bug.cgi?id=2161870#c3
___
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-Specio (rawhide). "Use SPDX-format license tag"

[notifications]

Notification time stamped 2023-01-24 16:24:21 UTC

From 7ab188b5c779ec958555b85546f486505a6d7f33 Mon Sep 17 00:00:00 2001
From: Paul Howarth 
Date: Jan 24 2023 16:24:09 +
Subject: Use SPDX-format license tag


---

diff --git a/perl-Specio.spec b/perl-Specio.spec
index 0fbc6c4..824720a 100644
--- a/perl-Specio.spec
+++ b/perl-Specio.spec
@@ -9,10 +9,10 @@ Name: perl-Specio
 Version:   0.48
 Release:   3%{?dist}
 Summary:   Type constraints and coercions for Perl
-# lib/Specio/PartialDump.pm:   GPL+ or Artistic
+# lib/Specio/PartialDump.pm:   GPL-1.0-or-later OR Artistic-1.0-Perl
 #  

-# other files: Artistic 2.0
-License:   Artistic 2.0 and (GPL+ or Artistic)
+# other files: Artistic-2.0
+License:   Artistic-2.0 AND (GPL-1.0-or-later OR Artistic-1.0-Perl)
 URL:   https://metacpan.org/release/Specio
 Source0:   
https://cpan.metacpan.org/modules/by-module/Test/Specio-%{version}.tar.gz
 BuildArch: noarch



https://src.fedoraproject.org/rpms/perl-Specio/c/7ab188b5c779ec958555b85546f486505a6d7f33?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

Re: [Test-Announce] Heads up: testing requested for significant PackageKit update

[Michael Catanzaro]

On Mon, Jan 23 2023 at 09:27:08 PM -0800, Gordon Messmer 
 wrote:

Time will tell if that's credit or blame.  LOL.

Sincerely, though, I know I'm not the first person to work on tackling
this, and I can't take all of the credit.


Good, since I fear it's going to be blame. :D I have unfortunately 
pulled the update as Lukas posted a screenshot of GNOME Software 
getting out of sync with dnf.


Michael

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

Re: FYI xz 5.4.1 in Fedora updates (F36, F37, Rawhide)

[Miro Hrončok]

On 24. 01. 23 16:20, Miro Hrončok wrote:

On 23. 01. 23 15:39, Richard W.M. Jones wrote:


F36: https://bodhi.fedoraproject.org/updates/FEDORA-2023-d823c8dfb8

F37: https://bodhi.fedoraproject.org/updates/FEDORA-2023-8362bcf475

One package which is known to depend on the exact version of xz is
perl-Compress-Raw-Lzma.  The updates above should do the right thing.

As far as I'm aware there are no other packages that depend on the
exact version of xz (or liblzma) and no breaking changes to liblzma,
but if there are please let us know.


For the record, Pythons now FTBFS with:

==
FAIL: test_unzip_zipfile (test.test_shutil.TestArchives.test_unzip_zipfile)
--
Traceback (most recent call last):
   File "/builddir/build/BUILD/Python-3.12.0a4/Lib/test/test_shutil.py", line 
1514, in test_unzip_zipfile

     subprocess.check_output(zip_cmd, stderr=subprocess.STDOUT)
   File "/builddir/build/BUILD/Python-3.12.0a4/Lib/subprocess.py", line 466, in 
check_output

     return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
    ^
   File "/builddir/build/BUILD/Python-3.12.0a4/Lib/subprocess.py", line 571, in 
run

     raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['unzip', '-t', 
'/builddir/build/BUILD/Python-3.12.0a4/build/debug/build/test_python_64979æ/tmpau1avwr6/archive.zip']' returned non-zero exit status 80.

During handling of the above exception, another exception occurred:
Traceback (most recent call last):
   File "/builddir/build/BUILD/Python-3.12.0a4/Lib/test/test_shutil.py", line 
1520, in test_unzip_zipfile

     self.fail(msg.format(exc, details))
AssertionError: Command '['unzip', '-t', 
'/builddir/build/BUILD/Python-3.12.0a4/build/debug/build/test_python_64979æ/tmpau1avwr6/archive.zip']' returned non-zero exit status 80.

**Unzip Output**
Archive: 
/builddir/build/BUILD/Python-3.12.0a4/build/debug/build/test_python_64979æ/tmpau1avwr6/archive.zip

*** buffer overflow detected ***: terminated
--


I have not yet verified this is cuased by new xz, but it is one of the suspects.

https://koschei.fedoraproject.org/package/python3.12?collection=f38


I cannot reproduce this in mock just by updating xz, so it seems it is 
unrelated.

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

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

[tdawson]

Dear all,

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

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

A general agenda is the following:

#topic aloha

#topic EPEL Issues https://pagure.io/epel/issues
* https://pagure.io/epel/issues?tags=meeting=Open

#topic Old Business (if needed)

#topic General Issues / Open Floor




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

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

[Bug 2162301] perl-Net-Pcap-0.21 is available

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

   Fixed In Version||perl-Net-Pcap-0.21-1.fc38
 Status|ASSIGNED|CLOSED
 Resolution|--- |RAWHIDE
Last Closed||2023-01-24 15:58:55




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2162301
___
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

[rpms/perl-Net-Pcap] PR #1: 0.21 bump; Package tests

[Jitka Plesnikova]

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

Merged pull-request:

``
0.21 bump; Package tests
``

https://src.fedoraproject.org/rpms/perl-Net-Pcap/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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2163999] F38FailsToInstall: perl-SQL-Interp-tests

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

 Resolution|--- |RAWHIDE
   Doc Type|--- |If docs needed, set a value
   Fixed In Version||perl-SQL-Interp-1.27-9.fc38
 Status|NEW |CLOSED
 CC|jples...@redhat.com |
Last Closed||2023-01-24 15:56:10




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2163999
___
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 2163998] F38FailsToInstall: perl-LDAP-tests

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

 Resolution|--- |RAWHIDE
   Fixed In Version||perl-LDAP-0.68-10.fc38
 Status|NEW |CLOSED
Last Closed||2023-01-24 15:47:17



--- Comment #2 from Jitka Plesnikova  ---
(In reply to Miro Hrončok from comment #1)
> This reminds me bz2150992 a bit.
It's not the same issue, there was found dependency
'BEGIN {require './t/lifecycles/utils.pl'};'
and the relative imports (./) are ignored now.

For perl-LDAP-tests, it found this dependency
BEGIN { require "t/common.pl" }


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2163998
___
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

Re: FYI xz 5.4.1 in Fedora updates (F36, F37, Rawhide)

[Miro Hrončok]

On 23. 01. 23 15:39, Richard W.M. Jones wrote:


F36: https://bodhi.fedoraproject.org/updates/FEDORA-2023-d823c8dfb8

F37: https://bodhi.fedoraproject.org/updates/FEDORA-2023-8362bcf475

One package which is known to depend on the exact version of xz is
perl-Compress-Raw-Lzma.  The updates above should do the right thing.

As far as I'm aware there are no other packages that depend on the
exact version of xz (or liblzma) and no breaking changes to liblzma,
but if there are please let us know.


For the record, Pythons now FTBFS with:

==
FAIL: test_unzip_zipfile (test.test_shutil.TestArchives.test_unzip_zipfile)
--
Traceback (most recent call last):
  File "/builddir/build/BUILD/Python-3.12.0a4/Lib/test/test_shutil.py", line 
1514, in test_unzip_zipfile

subprocess.check_output(zip_cmd, stderr=subprocess.STDOUT)
  File "/builddir/build/BUILD/Python-3.12.0a4/Lib/subprocess.py", line 466, in 
check_output

return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
   ^
  File "/builddir/build/BUILD/Python-3.12.0a4/Lib/subprocess.py", line 571, in 
run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['unzip', '-t', 
'/builddir/build/BUILD/Python-3.12.0a4/build/debug/build/test_python_64979æ/tmpau1avwr6/archive.zip']' 
returned non-zero exit status 80.

During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/builddir/build/BUILD/Python-3.12.0a4/Lib/test/test_shutil.py", line 
1520, in test_unzip_zipfile

self.fail(msg.format(exc, details))
AssertionError: Command '['unzip', '-t', 
'/builddir/build/BUILD/Python-3.12.0a4/build/debug/build/test_python_64979æ/tmpau1avwr6/archive.zip']' 
returned non-zero exit status 80.

**Unzip Output**
Archive: 
/builddir/build/BUILD/Python-3.12.0a4/build/debug/build/test_python_64979æ/tmpau1avwr6/archive.zip

*** buffer overflow detected ***: terminated
--


I have not yet verified this is cuased by new xz, but it is one of the suspects.

https://koschei.fedoraproject.org/package/python3.12?collection=f38


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

List of long term FTBFS packages to be retired in February​

[Miro Hrončok]

Dear maintainers.

Based on the current fail to build from source policy, the following packages
should be retired from Fedora 38 approximately one week before branching.

5 weekly reminders are required, hence the retirement will happen
approximately in 2 weeks, i.e. around 2023-02-08.
Since this is unfortunately after the branching,
packages will be retired on rawhide and f38.

This is the second reminder. I apologize for starting this process a bit later 
than required.


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


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

This report is based on dist tags.

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

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

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

Package  (co)maintainers
===
ArpONfab, sagarun
IQmoljussilehtola
alevtlucilanga
bowtie   jaruga, verdurin
btkbdd   lkundrak
cave9jonathanspw
ccrypt   fab
cjdnssdgathman
datamash jhladky
erlpmd   peter
free42   brouhaha
frogrteuf
goddifab, go-sig
golang-github-adroll-goamz   eclipseo, go-sig
golang-github-aphistic-sweet eclipseo, go-sig
golang-github-aws-sdk-2-0.24 eclipseo, go-sig
golang-github-cheekybits-genny   eclipseo, go-sig
golang-github-cockroachdb-gostdlib   eclipseo, go-sig
golang-github-cosmos72-gomacro   go-sig, qulogic
golang-github-dave-dst   eclipseo, go-sig
golang-github-docker-licensing   eclipseo, go-sig
golang-github-gdamore-optopiafab, go-sig
golang-github-gopherjs   eclipseo, go-sig, jchaloup
golang-github-jung-kurt-gofpdf   eclipseo, go-sig
golang-github-latex  eclipseo, go-sig
golang-github-maruel-panicparse  eclipseo, go-sig
golang-github-maruel-panicparse-2eclipseo, go-sig
golang-github-mattermost-xml-roundtrip-validator eclipseo, go-sig
golang-github-mholt-certmagic-0.8eclipseo, go-sig
golang-gonum-1-plot  eclipseo, go-sig
golang-helm-3dcavalca, go-sig
golang-istio-pkg eclipseo, go-sig
golang-sigs-k8s-application  eclipseo, go-sig
golang-sigs-k8s-controller-runtime   eclipseo, go-sig
gtkhash  nonamedotc
howl atim, pwalter
httpdump fab, go-sig
ipmiutil arcress
irssi-xmpp   lbazan, maha
kguitar  davidcornette
kjotskde-sig, thunderbirdtr
kmplayer moceap, rdieter
libmobi  avsej
libmodulemd1 sgallagh
libndn-cxx   susmit
libsafec aekoroglu, jhli
libyami  kwizart
libyami-utilskwizart
llvm10   petersen, sergesanspaille
llvm11   jistone, petersen,
 sergesanspaille, tstellar
llvm12   petersen, sergesanspaille,
 tstellar
llvm9.0  jistone, petersen, tstellar
lucidlifepgordon
maven-scmmizdebsk, trawets
mimicpbrobinson
nall chkr
nodejs-tape  fab, patches
openas2  

List of long term FTBFS packages to be retired in February​

[Miro Hrončok]

Dear maintainers.

Based on the current fail to build from source policy, the following packages
should be retired from Fedora 38 approximately one week before branching.

5 weekly reminders are required, hence the retirement will happen
approximately in 2 weeks, i.e. around 2023-02-08.
Since this is unfortunately after the branching,
packages will be retired on rawhide and f38.

This is the second reminder. I apologize for starting this process a bit later 
than required.


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


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

This report is based on dist tags.

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

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

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

Package  (co)maintainers
===
ArpONfab, sagarun
IQmoljussilehtola
alevtlucilanga
bowtie   jaruga, verdurin
btkbdd   lkundrak
cave9jonathanspw
ccrypt   fab
cjdnssdgathman
datamash jhladky
erlpmd   peter
free42   brouhaha
frogrteuf
goddifab, go-sig
golang-github-adroll-goamz   eclipseo, go-sig
golang-github-aphistic-sweet eclipseo, go-sig
golang-github-aws-sdk-2-0.24 eclipseo, go-sig
golang-github-cheekybits-genny   eclipseo, go-sig
golang-github-cockroachdb-gostdlib   eclipseo, go-sig
golang-github-cosmos72-gomacro   go-sig, qulogic
golang-github-dave-dst   eclipseo, go-sig
golang-github-docker-licensing   eclipseo, go-sig
golang-github-gdamore-optopiafab, go-sig
golang-github-gopherjs   eclipseo, go-sig, jchaloup
golang-github-jung-kurt-gofpdf   eclipseo, go-sig
golang-github-latex  eclipseo, go-sig
golang-github-maruel-panicparse  eclipseo, go-sig
golang-github-maruel-panicparse-2eclipseo, go-sig
golang-github-mattermost-xml-roundtrip-validator eclipseo, go-sig
golang-github-mholt-certmagic-0.8eclipseo, go-sig
golang-gonum-1-plot  eclipseo, go-sig
golang-helm-3dcavalca, go-sig
golang-istio-pkg eclipseo, go-sig
golang-sigs-k8s-application  eclipseo, go-sig
golang-sigs-k8s-controller-runtime   eclipseo, go-sig
gtkhash  nonamedotc
howl atim, pwalter
httpdump fab, go-sig
ipmiutil arcress
irssi-xmpp   lbazan, maha
kguitar  davidcornette
kjotskde-sig, thunderbirdtr
kmplayer moceap, rdieter
libmobi  avsej
libmodulemd1 sgallagh
libndn-cxx   susmit
libsafec aekoroglu, jhli
libyami  kwizart
libyami-utilskwizart
llvm10   petersen, sergesanspaille
llvm11   jistone, petersen,
 sergesanspaille, tstellar
llvm12   petersen, sergesanspaille,
 tstellar
llvm9.0  jistone, petersen, tstellar
lucidlifepgordon
maven-scmmizdebsk, trawets
mimicpbrobinson
nall chkr
nodejs-tape  fab, patches
openas2  

[EPEL-devel] Re: gcc ee this bug on RHEL9 , How we reach RHEL team ?

[Josh Boyer]

On Tue, Jan 24, 2023 at 9:26 AM Troy Dawson  wrote:
>
> Just so people don't need to go to the bug.
> This has already been reported for RHEL 9.
> https://bugzilla.redhat.com/show_bug.cgi?id=2140266
>
> If I understand "Approved Release" correctly, the fix will come out in RHEL 
> 9.2

Most people can't see the field you're referencing.  The bug is in
VERIFIED state though, which means anyone should be able to test gcc
in CentOS Stream 9 and confirm if it's fixed right now.

josh
___
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] Re: gcc ee this bug on RHEL9 , How we reach RHEL team ?

[Troy Dawson]

Just so people don't need to go to the bug.
This has already been reported for RHEL 9.
https://bugzilla.redhat.com/show_bug.cgi?id=2140266

If I understand "Approved Release" correctly, the fix will come out in RHEL
9.2

On Tue, Jan 24, 2023 at 3:57 AM Sérgio Basto  wrote:

> https://bugzilla.redhat.com/show_bug.cgi?id=1996330#c14
> --
> Sérgio M. B.
> ___
> 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 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

[Bug 2163998] F38FailsToInstall: perl-LDAP-tests

[bugzilla]

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

Miro Hrončok  changed:

   What|Removed |Added

   Doc Type|--- |If docs needed, set a value
 CC||mhron...@redhat.com



--- Comment #1 from Miro Hrončok  ---
This reminds me bz2150992 a bit.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2163998
___
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 2161072] F38FailsToInstall: perl-PDF-Haru

[bugzilla]

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

Fedora Fails To Install  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|ASSIGNED|CLOSED
Last Closed||2023-01-24 14:08:23



--- Comment #2 from Fedora Fails To Install  ---
Hello,

Please note that this comment was generated automatically by
https://pagure.io/releng/blob/main/f/scripts/ftbfs-fti/follow-policy.py
If you feel that this output has mistakes, please open an issue at
https://pagure.io/releng/

All subpackages of a package against which this bug was filled are now
installable or removed from Fedora 38.

Thanks for taking care of it!


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2161072
___
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 2163999] New: F38FailsToInstall: perl-SQL-Interp-tests

[bugzilla]

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

Bug ID: 2163999
   Summary: F38FailsToInstall: perl-SQL-Interp-tests
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-SQL-Interp
  Assignee: jples...@redhat.com
  Reporter: fti-b...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: jples...@redhat.com,
perl-devel@lists.fedoraproject.org
Blocks: 2117177 (F38FailsToInstall,RAWHIDEFailsToInstall)
  Target Milestone: ---
Classification: Fedora



Hello,

Please note that this comment was generated automatically by
https://pagure.io/releng/blob/main/f/scripts/ftbfs-fti/follow-policy.py
If you feel that this output has mistakes, please open an issue at
https://pagure.io/releng/

Your package (perl-SQL-Interp) Fails To Install in Fedora 38:

can't install perl-SQL-Interp-tests:
  - nothing provides perl(t::lib.pl) needed by
perl-SQL-Interp-tests-1.27-8.fc38.noarch

If you know about this problem and are planning on fixing it, please
acknowledge so by setting the bug status to ASSIGNED. If you don't have time to
maintain this package, consider orphaning it, so maintainers of dependent
packages realize the problem.


If you don't react accordingly to the policy for FTBFS/FTI bugs
(https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/),
your package may be orphaned in 8+ weeks.


P.S. The data was generated solely from koji buildroot, so it might be newer
than the latest compose or the content on mirrors. To reproduce, use the
koji/local repo only, e.g. in mock:

$ mock -r fedora-38-x86_64 --config-opts mirrored=False install
perl-SQL-Interp-tests


P.P.S. If this bug has been reported in the middle of upgrading multiple
dependent packages, please consider using side tags:
https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#updating-inter-dependent-packages

Thanks!



Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=2117177
[Bug 2117177] Fedora 38 Fails To install Tracker
-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2163999
___
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 2163998] New: F38FailsToInstall: perl-LDAP-tests

[bugzilla]

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

Bug ID: 2163998
   Summary: F38FailsToInstall: perl-LDAP-tests
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-LDAP
  Assignee: jples...@redhat.com
  Reporter: fti-b...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: caol...@redhat.com, jples...@redhat.com, ka...@ucw.cz,
mspa...@redhat.com,
perl-devel@lists.fedoraproject.org,
rhug...@redhat.com, rstr...@redhat.com,
sandm...@redhat.com
Blocks: 2117177 (F38FailsToInstall,RAWHIDEFailsToInstall)
  Target Milestone: ---
Classification: Fedora



Hello,

Please note that this comment was generated automatically by
https://pagure.io/releng/blob/main/f/scripts/ftbfs-fti/follow-policy.py
If you feel that this output has mistakes, please open an issue at
https://pagure.io/releng/

Your package (perl-LDAP) Fails To Install in Fedora 38:

can't install perl-LDAP-tests:
  - nothing provides perl(t::common.pl) needed by
perl-LDAP-tests-1:0.68-9.fc38.noarch

If you know about this problem and are planning on fixing it, please
acknowledge so by setting the bug status to ASSIGNED. If you don't have time to
maintain this package, consider orphaning it, so maintainers of dependent
packages realize the problem.


If you don't react accordingly to the policy for FTBFS/FTI bugs
(https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/),
your package may be orphaned in 8+ weeks.


P.S. The data was generated solely from koji buildroot, so it might be newer
than the latest compose or the content on mirrors. To reproduce, use the
koji/local repo only, e.g. in mock:

$ mock -r fedora-38-x86_64 --config-opts mirrored=False install
perl-LDAP-tests


P.P.S. If this bug has been reported in the middle of upgrading multiple
dependent packages, please consider using side tags:
https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#updating-inter-dependent-packages

Thanks!



Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=2117177
[Bug 2117177] Fedora 38 Fails To install Tracker
-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2163998
___
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

Re: Fedora 38 mass rebuild is finished

[Artur Frenszek-Iwicki]

> cqrlog - Fails for some weird lazbuild issue I don't understand
This is most likely my fault, since Lazarus seems to be quite tightly coupled 
to specific FPC versions.
Historically, whenever we updated/rebuilt FPC, we'd also rebuilt Lazarus. This 
time, when I rebuilt
FPC as part of the repackaging change [1], I completely forgot about rebuilding 
Lazarus as well.

Since Lazarus eventually got rebuilt as part of the Mass Rebuild, I expect that
once lazarus-2.2.4-2.fc38 becomes available in the rawhide buildroot,
it should be possible to just re-submit the failed builds and they'll work this 
time.

Sorry about the mess.
A.FI.

[1] https://fedoraproject.org/wiki/Changes/F38-FPC-repackaging
___
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 38 mass rebuild is finished

[Vascom]

Need help with rebuilding doublecmd.

вт, 24 янв. 2023 г. в 16:21, Richard Shaw :
>
> hobbes1069 (9):
> cqrlog - Fails for some weird lazbuild issue I don't understand
> flnet - Spec conditional oops. Fixed.
> flrig - Needed cstdint. Fixed
> freecad - Needs cstdint. Working on it.
> gmsh - Needed cstdint. Fixed.
> openCOLLADA - error: possibly dangling reference to a temporary. Don't know 
> how to fix this one.
> opencascade - error: declaration of 'tbb::task& 
> tbb::internal::task_prefix::task()' changes meaning of 'task'
> openexr - Needed cstdint. Fixed.
> spnavcfg - https://github.com/FreeSpacenav/spnavcfg/issues/30
>
> 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, 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 38 mass rebuild is finished

[Richard Shaw]

hobbes1069 (9):
cqrlog - Fails for some weird lazbuild issue I don't understand
flnet - Spec conditional oops. Fixed.
flrig - Needed cstdint. Fixed
freecad - Needs cstdint. Working on it.
gmsh - Needed cstdint. Fixed.
openCOLLADA - error: possibly dangling reference to a temporary. Don't know
how to fix this one.
opencascade - error: declaration of 'tbb::task&
tbb::internal::task_prefix::task()' changes meaning of 'task'
openexr - Needed cstdint. Fixed.
spnavcfg - https://github.com/FreeSpacenav/spnavcfg/issues/30

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

Re: Build stuck on ppc64le

[Dan Horák]

On Tue, 24 Jan 2023 12:07:10 +
"Richard W.M. Jones"  wrote:

> https://koji.fedoraproject.org/koji/taskinfo?taskID=96612861
> 
> The build has completed already on other arches, but on ppc64le it has
> been stuck for ~ 45 minutes.  What's especially odd is that it has
> apparently picked a builder (so it's not stuck waiting for a free
> machine) but the builder isn't making progress.

I think the builder is on a host that's not responding currently, I
will free the task, so another active builder can pick it up


Dan

> 
> Rich.
> 
> -- 
> Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
> Read my programming and virtualization blog: http://rwmj.wordpress.com
> libguestfs lets you edit virtual machines.  Supports shell scripting,
> bindings from many languages.  http://libguestfs.org
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam, 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: List of long term FTBFS packages to be retired in February​

[Mikolaj Izdebski]

On Mon, Jan 23, 2023 at 12:22 AM Jerry James  wrote:
>
> On Fri, Jan 20, 2023 at 9:52 PM Jerry James  wrote:
> > > maven-scm  mizdebsk, trawets
> >
> > For those affected by this, I've made a COPR with a possible
> > resolution: 
> > https://copr.fedorainfracloud.org/coprs/jjames/buildnumber-maven-plugin/.
> > Things to note:
> >
> > - plexus-interactivity must be unretired.
> > - I first tried updating maven-scm to version 1.13.0, but it requires
> > an older version of jgit than we have in Fedora Rawhide.  It would not
> > build.  I had to go to 2.0.0-M3 to get a successful build.
> > - There is a possible XMvn bug affecting maven-scm.  See the comment
> > in the %build section.  There are duplicate entries in .xmvn-reactor
> > for every pom.xml that includes pom.  I'm not
> > certain if this is an XMvn bug, or if the maven-scm pom.xml files are
> > wrong somehow.
> > - buildnumber-maven-plugin version 1.4 was too old, so I moved all the
> > way to 3.0.0.  Even then, it needed a small patch to work with
> > maven-scm 2.0.0.
> >
> > Or we can all remove mvn-scm and buildnumber-maven-plugin from our
> > respective packages' POMs.
>
> I should note that I intend to do the latter for jakarta-json.  If
> somebody wants to keep maven-scm or buildnumber-maven-plugin in
> Fedora, feel free to take anything you want from that COPR, remove my
> name, and slap your own in there.  I'm not going to do it, however.

I am in favor of removing buildnumber-maven-plugin.
In all my packages this plugin is explicitly disabled as it is not
very useful for building Fedora packages.

--
Mikolaj Izdebski

>
> Regards,
> --
> Jerry James
> https://www.jamezone.org/
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam, 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

Ghostscript 10.0.0 rebase in side tag

[Richard Lescak]

Hi,

we are going to introduce new Ghostscript 10.0.0 with bumped soname into
the rawhide.
Rebuilds will be done in the tag 'f38-build-side-62054'.
Affected packages: xcircuit, libspectre, texlive-base, gimp, graphviz,
doxygen, ImageMagick
Maintainers were notified.

Best regards

-- 

Richard Lescak

Associate Software Engineer

Red Hat Czech - Brno TPB-C 

___
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] Re: gcc bug on RHEL9 , How we reach RHEL team ?

[Stephen Smoogen]

On Tue, 24 Jan 2023 at 07:11, Josh Boyer  wrote:

> On Tue, Jan 24, 2023 at 7:01 AM Sérgio Basto  wrote:
> >
> > Hi,
> > Sorry, now subject is correct, the gcc have one patch for the error
> > above, that is seen on rhel 9
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=1996330#c14
>
> If you believe this is present in RHEL 9, please clone the bug to the
> Red Hat Enterprise Linux 9 bugzilla family.
>
>
Also going from someone I pinged:

Please check if it is a duplicate of either bug first:

  gcc: Incorrect always_inline diagnostic in LTO mode with #pragma GCC
  target("cpu=power10")
  

  digikam builds fail with gcc 11.3.1-4 (target specific option mismatch)
  



-- 
Stephen Smoogen, Red Hat Automotive
Let us be kind to one another, for most of us are fighting a hard battle.
-- Ian MacClaren
___
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] Re: gcc bug on RHEL9 , How we reach RHEL team ?

[Josh Boyer]

On Tue, Jan 24, 2023 at 7:01 AM Sérgio Basto  wrote:
>
> Hi,
> Sorry, now subject is correct, the gcc have one patch for the error
> above, that is seen on rhel 9
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1996330#c14

If you believe this is present in RHEL 9, please clone the bug to the
Red Hat Enterprise Linux 9 bugzilla family.

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

[Bug 2162191] perl-Dist-Zilla-6.030 is available

[bugzilla]

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

Michal Josef Spacek  changed:

   What|Removed |Added

 Resolution|--- |RAWHIDE
 Status|ASSIGNED|CLOSED
Last Closed||2023-01-24 12:08:10




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2162191
___
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

Build stuck on ppc64le

[Richard W.M. Jones]

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

The build has completed already on other arches, but on ppc64le it has
been stuck for ~ 45 minutes.  What's especially odd is that it has
apparently picked a builder (so it's not stuck waiting for a free
machine) but the builder isn't making progress.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
libguestfs lets you edit virtual machines.  Supports shell scripting,
bindings from many languages.  http://libguestfs.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[EPEL-devel] gcc bug on RHEL9 , How we reach RHEL team ?

[Sérgio Basto]

Hi,
Sorry, now subject is correct, the gcc have one patch for the error
above, that is seen on rhel 9 

https://bugzilla.redhat.com/show_bug.cgi?id=1996330#c14


-- 
Sérgio M. B.
___
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

-- 
Sérgio M. B.
___
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] gcc ee this bug on RHEL9 , How we reach RHEL team ?

[Sérgio Basto]

https://bugzilla.redhat.com/show_bug.cgi?id=1996330#c14
-- 
Sérgio M. B.
___
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

Re: Fedora 38 mass rebuild is finished

[Tomas Hrcka]

done.

$ koji list-tagged eln libunistring
Build

libunistring-1.0-2.eln120
libunistring-1.0-2.fc37

On Tue, Jan 24, 2023 at 11:59 AM Tomáš Popela  wrote:
>
>
>
> On Mon, Jan 23, 2023 at 8:56 PM Kevin Fenzi  wrote:
>>
>> On Mon, Jan 23, 2023 at 01:36:10PM -0600, Jonathan Wright via devel wrote:
>> > I'm seeing the same errors on rawhide buildroot right now.
>>
>> The problem was libunistring-1.1-3.fc38 (again).
>>
>> We untagged it in december, but looks like no one followed up to get
>> dependent packages rebuilt:
>>
>> https://pagure.io/releng/issue/11175
>>
>> I have untagged it (again) for now.
>
>
> I see that the ELN buildroot is broken in the same way, can you Kevin or 
> Stephen untag the libunistring from ELN?
>
> Tom
>
>>
>>
>> kevin
>> ___
>> devel mailing list -- devel@lists.fedoraproject.org
>> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>> Fedora Code of Conduct: 
>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives: 
>> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
>> 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



-- 
Tomas Hrcka
role: CPE Team - Senior Software Engineer
fas: humaton
freenode: jednorozec
___
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 2162651] perl-Sub-Quote-2.006008 is available

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

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




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2162651
___
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

[rpms/perl-Net-Pcap] PR #1: 0.21 bump; Package tests

[Jitka Plesnikova]

jplesnik opened a new pull-request against the project: `perl-Net-Pcap` that 
you are following:
``
0.21 bump; Package tests
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Net-Pcap/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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Fedora 38 mass rebuild is finished

[Tomáš Popela]

On Mon, Jan 23, 2023 at 8:56 PM Kevin Fenzi  wrote:

> On Mon, Jan 23, 2023 at 01:36:10PM -0600, Jonathan Wright via devel wrote:
> > I'm seeing the same errors on rawhide buildroot right now.
>
> The problem was libunistring-1.1-3.fc38 (again).
>
> We untagged it in december, but looks like no one followed up to get
> dependent packages rebuilt:
>
> https://pagure.io/releng/issue/11175
>
> I have untagged it (again) for now.
>

I see that the ELN buildroot is broken in the same way, can you Kevin or
Stephen untag the libunistring from ELN?

Tom


>
> kevin
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> 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 38 mass rebuild is finished

[Zbigniew Jędrzejewski-Szmek]

On Tue, Jan 24, 2023 at 08:13:56AM +, Tom Hughes via devel wrote:
> On 24/01/2023 07:28, Jeff Law wrote:
> > 
> > 
> > On 1/24/23 00:16, Jakub Jelinek wrote:
> > > On Tue, Jan 24, 2023 at 10:00:47AM +0300, Vascom wrote:
> > > > I have some packages failed.
> > > > One of them libtins. Problem is that:
> > > > 
> > > > error: 'uint32_t' is not a member of 'std';
> > > > 
> > > > Is it normal? Is it GCC 13 change?
> > > 
> > > See
> > > https://gcc.gnu.org/gcc-13/porting_to.html#header-dep-changes
> > > Some libstdc++ headers included  in older versions
> > > as an implementation detail but no longer do.
> > > 
> > > Including stdint.h will introduce ::uint32_t type among others,
> > > but not std::uint32_t, if you use the latter, you need to
> > > include .
> > I've got a partial list of packages affected by the ongoing header
> > cleanups in libstdc++:
> 
> mapnik was affected as well but I fixed it last night.

dolfin had the same issue and I fixed it now. Thanks for the hint.

Zbyszek
___
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 38 mass rebuild is finished

[Jonathan Wakely]

On Tue, 24 Jan 2023 at 07:01, Vascom  wrote:
>
> I have some packages failed.
> One of them libtins. Problem is that:
>
> error: 'uint32_t' is not a member of 'std';
>
> Is it normal? Is it GCC 13 change?
>
> I must patch sources now?
> sed -i 's|stdint.h|cstdint|' include/tins/ip_address.h

std::uint32_t is defined in . If the sources don't include
that header, that is a bug.

This is the same thing we have mass rebuild: C and C++ code must
include the headers for the features it uses.

If you get an error saying something is not declared, make sure the
right header is included.
___
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

Schedule for Tuesday's FESCo Meeting (2023-01-24)

[Zbigniew Jędrzejewski-Szmek]

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

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

or run:
  date -d '2023-01-24 17:00 UTC'


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

= Discussed and Voted in the Ticket =


#2935 Change: TeXLive2022
https://pagure.io/fesco/issue/2935
APPROVED (+4,0,-0)

#2933 Change: FPC repackaging
https://pagure.io/fesco/issue/2933
APPROVED (+5,0,-0)

#2932 Change: GNU Toolchain Update (gcc 13.0, binutils 2.39, glibc 2.37, gdb 
12.1)
https://pagure.io/fesco/issue/2932
APPROVED (+6,0,-0)

#2931 Change: Noto Fonts For More Languages
https://pagure.io/fesco/issue/2931
APPROVED (+5,0,-0)


= Followups =


= New business =

#2934 Restore Provides: singularity to apptainer packaging
https://pagure.io/fesco/issue/2934

= Open Floor = 

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

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

[rpms/perl-Dist-Zilla] PR #2: 6.030 bump

[Michal Josef Špaček]

mspacek merged a pull-request against the project: `perl-Dist-Zilla` that you 
are following.

Merged pull-request:

``
6.030 bump
``

https://src.fedoraproject.org/rpms/perl-Dist-Zilla/pull-request/2
___
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

Re: Fedora 38 mass rebuild is finished

[Zbigniew Jędrzejewski-Szmek]

On Mon, Jan 23, 2023 at 06:52:30PM -0800, Kevin Fenzi wrote:
> On Mon, Jan 23, 2023 at 10:26:18PM +, Sérgio Basto wrote:
> > 
> > I found more 5 with
> > https://koji.fedoraproject.org/koji/tasks?owner=releng=active=tree=all=-id
> > 
> > 96481236 build (f38-rebuild,
> > /rpms/yaksa.git:528d57e3c954abfedba6f530f5ac09abaa9170fa)
> > 
> > 96474133 build (f38-rebuild, /rpms/trace-
> > cmd.git:d9631ac81ad4f30b7ca5ed8a7d3b57131c545080)
> > 
> > 96404064 build (f38-rebuild, /rpms/perl-
> > SDL.git:347cf3fb5ac90e14b96381722bc335744077e967)
> > 
> > 96383273 build (f38-rebuild,
> > /rpms/octave.git:93e5fb4a813805c66ec7107da26be2d52039106d
> > 
> > 96368979 build (f38-rebuild,
> > /rpms/libtracecmd.git:121d11cfd26c3a0d61671b83f32b0be1ec75f1ff)
> 
> Yes, I have canceled all those now. 

I started builds for all of those now.

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

[rpms/perl-Dist-Zilla] PR #2: 6.030 bump

[Michal Josef Špaček]

mspacek opened a new pull-request against the project: `perl-Dist-Zilla` that 
you are following:
``
6.030 bump
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Dist-Zilla/pull-request/2
___
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 2162191] perl-Dist-Zilla-6.030 is available

[bugzilla]

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

Michal Josef Spacek  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
   Doc Type|--- |If docs needed, set a value



--- Comment #1 from Michal Josef Spacek  ---
Changes:

6.030 2023-01-18 21:36:40-05:00 America/New_York
- "dzil new" will use command line options before configuration
- "dzil add" now falls back to %Mint stash options before defaults
  (for both of the above: thanks, Graham Knop!)

For rawhide.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2162191
___
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 2160057] perl-WWW-Curl-4.17-31.fc38 FTBFS: curlopt-constants.c:19:51: error: 'CURL_DEPRECATED' undeclared

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

 Resolution|--- |RAWHIDE
 Status|MODIFIED|CLOSED
Last Closed||2023-01-24 09:31:24




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2160057
___
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

Re: gcc: RPM_ARCH not defined

[Lukas Javorsky]

Thank you, Tomas,

Great investigation.

Your suggested hack really fixed my issue.

On Mon, Jan 23, 2023 at 3:46 PM Tomas Korbar  wrote:

> Hello,
> since i encountered this in the past and postponed it, I did a bit of a
> digging and found this:
> As you probably found out by now it is caused by package-notes being
> dependent
> on environment variables that are expected to be present during package
> build.
> See the actual package-notes file contents:
> $ cat /usr/lib/rpm/redhat/redhat-package-notes
> *link:
> +
> --package-metadata={\"type\":\"rpm\",\"name\":\"%:getenv(RPM_PACKAGE_NAME
> \",\"version\":\"%:getenv(RPM_PACKAGE_VERSION -%:getenv(RPM_PACKAGE_RELEASE
> \",\"architecture\":\"%:getenv(RPM_ARCH
> \",\"osCpe\":\"cpe:/o:fedoraproject:fedora:38\"}
>
> I took a look at your test and found out that your test uses rpmbuild to
> perform
> preparation of sources:
> rlRun "rpmbuild -bp libarchive.spec"
> rlRun "rpmbuild -bc libarchive.spec"
> rlRun "popd"
>
> This probably executes configure in a way that configures linking to be
> done with "-specs=/usr/lib/rpm/redhat/redhat-package-notes" option and thus
> you now need the environment variables that the file mentions. These
> variables
> are defined and exported before build stage in macro defined in file
> /usr/lib/rpm/macros and if you would have executed the check phase with
> rpmbuild command, you would propably face no issue (did not verify this).
> Unfortunately the test performs check manually:
> rlRun "make check &> $TmpDir/make_check.log" 0 "Make check"
> rlRun -s "./libarchive_test"
> rlAssertGrep "Tests failed:[[:blank:]]* 0" $rlRun_LOG
> and thus there are no environment variables.
> This can be fixed by a little bit of a hack. Add this line:
> rlRun 'eval "$(rpm --eval %___build_pre)"; cd
> ~/rpmbuild/BUILD/libarchive-*' 0 "setting environment"
>
> before the make check and you are good to go. This causes
> that needed environment variables will be defined.
>
> I hope that this helps you or based on this information you will be able
> to find a better solution.
>
> Best Regards.
>
>
> On Mon, Jan 23, 2023 at 2:00 PM Mamoru TASAKA 
> wrote:
>
>> Mamoru TASAKA wrote on 2023/01/23 21:54:
>> > Lukas Javorsky wrote on 2023/01/23 21:39:
>> >> Hi,
>> >>
>> >> I've been looking at our upstreamed test [1] for libarchive package
>> and it
>> >> started to fail since Fedora 37.
>> >>
>> >> The error is: "gcc: fatal error: environment variable 'RPM_ARCH' not
>> defined
>> >> "
>> >>
>> >> Prior to the Fedora 37 the test was passing without any issue.
>> >>
>> >> Did anyone here had a similar problem?
>> >> Or could anyone help me find out what has changed so it's causing this
>> >> issue?
>> >>
>> >> [1]
>> >>
>> https://src.fedoraproject.org/tests/libarchive/blob/main/f/Sanity/Basic-sanity-test-for-libarchive
>> >>
>> >> Thank you so much for your help
>> >
>> > Most possibly due to "package note".
>> >
>> > `rpmbuild -bc` defines  %{_package_note_flags}, embeds
>> "-specs=/usr/lib/rpm/redhat/redhat-package-notes"
>> > to LDFLAGS, which needs "RPM_ARCH" environment. During rpmbuild
>> process, this environment is provided,
>> > but then later "make" process does not define this automatically
>> (because this process is not under
>> > "rpmbuild"), so embedded
>> "-specs=/usr/lib/rpm/redhat/redhat-package-notes" LDFLAGS complains about
>> > missing environment.
>> >
>> > (Yes, I think this is annoying - sometimes rpmbuild fails with some
>> reason, I try to fix compilation error
>> >   then try executing "make" locally, then I see linker complains about
>> "'RPM_ARCH' not defined"...)
>> >
>> > I usually write "%_package_note_flags %nil" to ~/.rpmmacros, not sure
>> if rpmbuild command line can
>> > undefine macros.
>> >
>>
>> Or maybe changing to "rpmbuild --define '_package_note_flags %nil' -bc
>> libarchive.spec" can fix the
>> issue you see.
>>
>> 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, 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:
> 

Re: Most OCaml packages have broken deps now

[Richard W.M. Jones]

This is running now:

https://koji.fedoraproject.org/koji/builds?inherited=0=62208=-build_id=1

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
libguestfs lets you edit virtual machines.  Supports shell scripting,
bindings from many languages.  http://libguestfs.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Fedora 38 mass rebuild is finished

[Tom Hughes via devel]

On 24/01/2023 07:28, Jeff Law wrote:



On 1/24/23 00:16, Jakub Jelinek wrote:

On Tue, Jan 24, 2023 at 10:00:47AM +0300, Vascom wrote:

I have some packages failed.
One of them libtins. Problem is that:

error: 'uint32_t' is not a member of 'std';

Is it normal? Is it GCC 13 change?


See
https://gcc.gnu.org/gcc-13/porting_to.html#header-dep-changes
Some libstdc++ headers included  in older versions
as an implementation detail but no longer do.

Including stdint.h will introduce ::uint32_t type among others,
but not std::uint32_t, if you use the latter, you need to
include .
I've got a partial list of packages affected by the ongoing header 
cleanups in libstdc++:


mapnik was affected as well but I fixed it last night.

Tom

--
Tom Hughes (t...@compton.nu)
http://compton.nu/
___
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