Re: RFC: Roadmap for DNF5 in Fedora 39 / invoking the Contingency Mechanism
> On 7/17/23 07:39, Jaroslav Mracek wrote: > > Hi, I put more details in the fesco ticket: > https://pagure.io/fesco/issue/3039#comment-864686 I believe these are > commonly known so I did not open any ticket against dnf5. > > As said in the comment, I stopped putting effort into making dnf5 work > for our use case (which is provisioning of multiple distributions for > upstream PR CI via ansible), we would certainly hit more issues - or > unimplemented functionality if you want to sugar coat it - that would > require workarounds. I have a great news dnf5-5.1.0-1.fc39 is in stable. The version 5.1 is the first version with stable API. Best regards Jarda ___ 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: RFC: Roadmap for DNF5 in Fedora 39 / invoking the Contingency Mechanism
> On Mon, Jul 17, 2023 at 6:40 AM Jaroslav Mracek wrote: > > Except dnf5 broke a number of microdnf usecases with low memory where > microdnf worked [1]. > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=2214520 Correct but as you can see the issue was not in DNF5 but in libsolv (solver for DNF, DNF5, zypper, PackageKit). Ales Matej from DNF team prepared two patches - one to resolve the issue in libsolv and second to enable workaround for DNF5. Thanks to better DNF5 structure we were able to discover the real cause of the issue. Therefore I am curios why the issue is mentioned here? Best 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
[Bug 2222638] F39FailsToInstall: perl-Tk
https://bugzilla.redhat.com/show_bug.cgi?id=638 Fedora Fails To Install changed: What|Removed |Added Resolution|--- |WORKSFORME Status|NEW |CLOSED Last Closed||2023-07-19 04:51:00 --- Comment #4 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 39. 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=638 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%20638%23c4 ___ 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 2222639] F39FailsToInstall: perl-Tk-TableMatrix
https://bugzilla.redhat.com/show_bug.cgi?id=639 Bug 639 depends on bug 638, which changed state. Bug 638 Summary: F39FailsToInstall: perl-Tk https://bugzilla.redhat.com/show_bug.cgi?id=638 What|Removed |Added Status|NEW |CLOSED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=639 ___ 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 2219205] perl-Module-CoreList-5.20230520 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2219205 Fedora Update System changed: What|Removed |Added Fixed In Version|perl-Module-CoreList-5.2023 |perl-Module-CoreList-5.2023 |0520-1.fc39 |0520-1.fc39 |perl-Module-CoreList-5.2023 |perl-Module-CoreList-5.2023 |0520-1.fc38 |0520-1.fc38 ||perl-Module-CoreList-5.2023 ||0520-1.fc37 --- Comment #6 from Fedora Update System --- FEDORA-2023-506d9f509d has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2219205 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202219205%23c6 ___ 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 2219205] perl-Module-CoreList-5.20230520 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2219205 Fedora Update System changed: What|Removed |Added Status|ON_QA |CLOSED Fixed In Version|perl-Module-CoreList-5.2023 |perl-Module-CoreList-5.2023 |0520-1.fc39 |0520-1.fc39 ||perl-Module-CoreList-5.2023 ||0520-1.fc38 Resolution|--- |ERRATA Last Closed||2023-07-19 03:13:41 --- Comment #5 from Fedora Update System --- FEDORA-2023-aaf41d7282 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2219205 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202219205%23c5 ___ 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: Orphaned packages looking for new maintainers
Hello, On Mon, Jul 17, 2023 at 8:49 PM Miro Hrončok wrote: > > switcheroo-controlorphan 2 weeks ago Has anyone from the Workstation WG noticed this? Won't losing switcheroo-control be a considerable usability regression? At the same time, the upstream developer is/was Bastien, which complicates things. ___ 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: Should we provide current/previous release links in URLs?
On Tue, Jul 18, 2023 at 01:58:09PM -0700, Adam Williamson wrote: > On Tue, 2023-07-18 at 13:42 -0700, Kevin Fenzi wrote: > > On Mon, Jul 17, 2023 at 05:59:50PM -0600, Orion Poplawski wrote: > > > As part of the cobbler project testing, we need to test accessing Fedora > > > releases with various URLs: > > > > > > "http://download.fedoraproject.org/pub/fedora/linux/releases/35/Everything/x86_64/os;, > > > "https://mirrors.fedoraproject.org/mirrorlist?repo=fedora-35=x86_64; > > > "https://mirrors.fedoraproject.org/metalink?repo=fedora-35=x86_64;, > > > > > > These need to get updated continuously as Fedora progresses. Could we > > > perhaps have a "current" and "previous" (or similar) that tracks the most > > > recent and previous release? > > > > Could we? Sure... but... there's a big can of worms around the source of > > truth as to what releases are in what state. We could add yet another > > thing that we have to manually update here I suppose. Not a super fan of > > that. > > > > Someday I hope we will finally solve that... > > well...could we possibly engineer this in such a way that it ultimately > keys off the definitions in the infra ansible repo? e.g. perhaps these > kinda aliases could be defined in a config file for mirrormanager, and > we could deploy such a config file from ansible? Yeah, at least that would not add any more things to update. ;) 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
Re: Should we provide current/previous release links in URLs?
On Tue, 2023-07-18 at 13:42 -0700, Kevin Fenzi wrote: > On Mon, Jul 17, 2023 at 05:59:50PM -0600, Orion Poplawski wrote: > > As part of the cobbler project testing, we need to test accessing Fedora > > releases with various URLs: > > > > "http://download.fedoraproject.org/pub/fedora/linux/releases/35/Everything/x86_64/os;, > > "https://mirrors.fedoraproject.org/mirrorlist?repo=fedora-35=x86_64; > > "https://mirrors.fedoraproject.org/metalink?repo=fedora-35=x86_64;, > > > > These need to get updated continuously as Fedora progresses. Could we > > perhaps have a "current" and "previous" (or similar) that tracks the most > > recent and previous release? > > Could we? Sure... but... there's a big can of worms around the source of > truth as to what releases are in what state. We could add yet another > thing that we have to manually update here I suppose. Not a super fan of > that. > > Someday I hope we will finally solve that... well...could we possibly engineer this in such a way that it ultimately keys off the definitions in the infra ansible repo? e.g. perhaps these kinda aliases could be defined in a config file for mirrormanager, and we could deploy such a config file from ansible? -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net ___ 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: Should we provide current/previous release links in URLs?
On Mon, Jul 17, 2023 at 05:59:50PM -0600, Orion Poplawski wrote: > As part of the cobbler project testing, we need to test accessing Fedora > releases with various URLs: > > "http://download.fedoraproject.org/pub/fedora/linux/releases/35/Everything/x86_64/os;, > "https://mirrors.fedoraproject.org/mirrorlist?repo=fedora-35=x86_64; > "https://mirrors.fedoraproject.org/metalink?repo=fedora-35=x86_64;, > > These need to get updated continuously as Fedora progresses. Could we > perhaps have a "current" and "previous" (or similar) that tracks the most > recent and previous release? Could we? Sure... but... there's a big can of worms around the source of truth as to what releases are in what state. We could add yet another thing that we have to manually update here I suppose. Not a super fan of that. Someday I hope we will finally solve that... 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
[Bug 2223772] New: perl-Business-ISBN-Data-20230718.001 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2223772 Bug ID: 2223772 Summary: perl-Business-ISBN-Data-20230718.001 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Business-ISBN-Data Keywords: FutureFeature, Triaged Assignee: jples...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: jples...@redhat.com, ka...@ucw.cz, mspa...@redhat.com, p...@city-fan.org, perl-devel@lists.fedoraproject.org Target Milestone: --- Classification: Fedora Releases retrieved: 20230718.001 Upstream release that is considered latest: 20230718.001 Current version/release in rawhide: 20230714.001-1.fc39 URL: https://metacpan.org/dist/Business-ISBN-Data/ 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/2674/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/perl-Business-ISBN-Data -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2223772 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202223772%23c0 ___ 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 2222638] F39FailsToInstall: perl-Tk
https://bugzilla.redhat.com/show_bug.cgi?id=638 Dan Horák changed: What|Removed |Added CC||d...@danny.cz --- Comment #3 from Dan Horák --- We might have some chance to get more data with the composes before the perl 5.38 introduction into f39 on July 13th ... It might show if it's the new perl or something else introduced earlier. Last successful perl-Tk-804.036-9.eln127 was from June 27th. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=638 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%20638%23c3 ___ 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-review workarounds for dnf5
On Tue, Jul 18, 2023 at 7:28 AM Fabio Valentini wrote:
> On Tue, Jul 18, 2023, 15:22 Maxwell G wrote:
>> --requires --resolve resolves the entire dependency tree of a package.
>> --requires just prints the direct dependencies that are specified in the
>> RPM metadata.
>> I don't know what this code is used for,
>> but I don't think simply removing --resolve is the right solution.
>
>
> Is it though? I assume you're thinking of "--recursive". As far as I know,
> "--requires --resolve" force resolution of virtual provides instead. I don't
> think removing "--resolve" is the correct solution for this case.
>
> For example, the check if a package depends on something that's deprecated
> (i.e. "Provides: deprecated ()") would need to resolve and check the actual
> package dependencies, not only virtual provides.
That's the reason for the second change I proposed, namely changing
line 97 from:
name = line.rsplit(".", 2)[0]
to:
name = resolve_one(line)[0].rsplit(".", 2)[0]
The `resolve_one` function resolves the dependencies one at a time, to
compensate for unavailability of the --resolve option. On second
thought, though, perhaps that code should be:
for arg in resolve_one(line):
name = arg.rsplit(".", 2)[0]
deps.append(name.rsplit("-", 2)[0])
--
Jerry James
http://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
Re: Say goodbye to polymake
On Tue, Jul 18, 2023 at 5:41 AM Richard W.M. Jones wrote: > The first error is: > > /home/rjones/d/fedora/polymake/rawhide/polymake-4.10/lib/core/src/perl/RefHash.xxs:737:11: > error: ‘Perl_ck_fun’ was not declared in this scope; did you mean > ‘Perl_cx_dup’? > 737 |return Perl_ck_fun(aTHX_ o); > | ^~~ > | Perl_cx_dup > ninja: build stopped: subcommand failed. > > As far as I can see that's the only missing / hidden Perl symbol. > > This symbol was hidden in: > https://github.com/Perl/perl5/commit/0351a629e71de127cbfd1b142e9eaa6069deabf5 > > As for what it does, that's more tricky. I believe what it's doing is > while Perl is parsing the input script, it is used to check that the > thing you are calling is a function. Unfortunately it's slightly more > complicated than that because it can convert some function-like things > to functions (returning the updated OP*). Also Perl_ck_fun is > complicated, to say the least: > > https://github.com/Perl/perl5/blob/a6d10131eee6ee336e4bd63f22a378e9d5ae40bd/op.c#L12522 > > For these reasons we can't just replace 'return Perl_ck_fun(aTHX_ o)' > with 'return aTHX_ o', nor can be copy the function into the polymake > source (since it calls other internal functions, but also for > licensing reasons). > > So I think this does require upstream attention. The code also calls save_pushptrptr (Pel_save_pushptrptr), another hidden symbol. Polymake has long had way too much knowledge of perl internals, which is why it has tended to break whenever a new perl version was released. It broke drastically this time. > Another note is this package requires ocaml-tplib which we orphaned. Right. I was going to remove that dependency, but the package broke from the perl update while we were still doing the OCaml 5 builds, so I never got the chance. At this point, I don't see how to keep it in Fedora until upstream does some major surgery on their code base. Thanks for looking at it! -- Jerry James http://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
Re: Orphaned packages looking for new maintainers
Dne 17. 07. 23 v 20:48 Miro Hrončok napsal(a): rpkg-macros orphan 2 weeks ago Copr team is taking this one as it is dependence of rpkg. Which is used in Copr. But we will be actively investigating how to replace rpkg in Copr. Unless somebody will take over the maintenance. Both in upstream and downstream. -- Miroslav Suchy, RHCA Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys ___ 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
Dear all, You are kindly invited to the meeting: EPEL Steering Committee on 2023-07-19 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
Re: Orphaned python-testing.postgresql
In response, I have also orphaned python-testing.common.database: - since python-testing.postgresql was the only package that depended on it (python-testing.mysqld was never packaged) - since nothing depends on python-testing.postgresql anymore, and - since upstream for these packages has been inactive for 4-5 years I think it’s probably best to let these packages go, but anyone considering picking them up should know that both packages have spec files that use modern practices and are in a good “state of repair.” - Ben Beasley (FAS: music) On 7/18/23 2:47 AM, Miroslav Suchý wrote: I orphaned https://src.fedoraproject.org/rpms/python-testing.postgresql I do not use it any more. Feel free to grab 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: fedora-review workarounds for dnf5
On Tue Jul 18, 2023 at 15:27 +0200, Fabio Valentini wrote: > On Tue, Jul 18, 2023, 15:22 Maxwell G wrote: > > > On Tue Jul 18, 2023 at 12:38 +0200, Jakub Kadlcik wrote: > > > Hello Jerry, > > > I proposed a workaround a few days ago > > > https://pagure.io/FedoraReview/pull-request/485 > > > > > > but your patch looks like a proper fix. I'll try it and merge to the > > > fedora-review codebase. > > > > > > Does anybody know what was the purpose of --resolve and if it will be > > > no problem when we remove it? > > > > --requires --resolve resolves the entire dependency tree of a package. > > --requires just prints the direct dependencies that are specified in the > > RPM metadata. > > I don't know what this code is used for, > > but I don't think simply removing --resolve is the right solution. > > > > Is it though? I assume you're thinking of "--recursive". As far as I know, > "--requires --resolve" force resolution of virtual provides instead. I > don't think removing "--resolve" is the correct solution for this case. > > For example, the check if a package depends on something that's deprecated > (i.e. "Provides: deprecated ()") would need to resolve and check the actual > package dependencies, not only virtual provides. > > Fabio Indeed. You're right! -- Maxwell G (@gotmax23) Pronouns: He/They ___ 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-review workarounds for dnf5
On Tue, Jul 18, 2023, 15:22 Maxwell G wrote: > On Tue Jul 18, 2023 at 12:38 +0200, Jakub Kadlcik wrote: > > Hello Jerry, > > I proposed a workaround a few days ago > > https://pagure.io/FedoraReview/pull-request/485 > > > > but your patch looks like a proper fix. I'll try it and merge to the > > fedora-review codebase. > > > > Does anybody know what was the purpose of --resolve and if it will be > > no problem when we remove it? > > --requires --resolve resolves the entire dependency tree of a package. > --requires just prints the direct dependencies that are specified in the > RPM metadata. > I don't know what this code is used for, > but I don't think simply removing --resolve is the right solution. > Is it though? I assume you're thinking of "--recursive". As far as I know, "--requires --resolve" force resolution of virtual provides instead. I don't think removing "--resolve" is the correct solution for this case. For example, the check if a package depends on something that's deprecated (i.e. "Provides: deprecated ()") would need to resolve and check the actual package dependencies, not only virtual provides. Fabio > -- > Maxwell G (@gotmax23) > Pronouns: He/They > ___ > 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-scm-requests email
On Tue Jul 18, 2023 at 13:47 +0200, Fabio Valentini wrote: > On Tue, Jul 18, 2023 at 4:38 AM Maxwell G wrote: > > > > Hi, > > > > It seems the fedora-scm-requests processor is creating the initial > > repository commits with `releng bot ` as the > > committer. Does anyone know where this is coming from? Should it be > > changed to something @fedoraproject.org? > > Yeah this is really weird, I see it now in my packages too ... > Earliest package created by releng-bot I could find quickly: > https://src.fedoraproject.org/rpms/rust-pyo3_0.15/c/fc77732c9f43bc7d472ae1c7de15bf9f90e2b730?branch=rawhide > > So indeed seems to have been this way since the start. Yeah, I also noticed this from the beginning and found it strange. I requested some packages yesterday, and it occurred to me that maybe this wasn't intentional and I should report it :). -- Maxwell G (@gotmax23) Pronouns: He/They ___ 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-review workarounds for dnf5
On Tue Jul 18, 2023 at 12:38 +0200, Jakub Kadlcik wrote: > Hello Jerry, > I proposed a workaround a few days ago > https://pagure.io/FedoraReview/pull-request/485 > > but your patch looks like a proper fix. I'll try it and merge to the > fedora-review codebase. > > Does anybody know what was the purpose of --resolve and if it will be > no problem when we remove it? --requires --resolve resolves the entire dependency tree of a package. --requires just prints the direct dependencies that are specified in the RPM metadata. I don't know what this code is used for, but I don't think simply removing --resolve is the right solution. -- Maxwell G (@gotmax23) Pronouns: He/They ___ 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-scm-requests email
On Tue, Jul 18, 2023 at 4:38 AM Maxwell G wrote: > > Hi, > > It seems the fedora-scm-requests processor is creating the initial > repository commits with `releng bot ` as the > committer. Does anyone know where this is coming from? Should it be > changed to something @fedoraproject.org? Yeah this is really weird, I see it now in my packages too ... Earliest package created by releng-bot I could find quickly: https://src.fedoraproject.org/rpms/rust-pyo3_0.15/c/fc77732c9f43bc7d472ae1c7de15bf9f90e2b730?branch=rawhide So indeed seems to have been this way since the start. Fabio ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Say goodbye to polymake
On Tue, Jul 18, 2023 at 08:27:19AM +0100, Richard W.M. Jones wrote: > On Tue, Jul 18, 2023 at 08:23:54AM +0100, Richard W.M. Jones wrote: > > On Mon, Jul 17, 2023 at 04:13:59PM -0600, Jerry James wrote: > > > The introduction of perl 5.38.0 broke polymake beyond repair. Several > > > symbols formerly used by polymake have been marked as internal APIs. > > > They now have the ELF hidden attribute, so we can't even cheat by > > > adding prototypes to the polymake code. > > > > Do you have a list of the deprecated APIs they are using? Or a link > > to a bug on the topic? I happen to have far too much experience of > > Perl internals and I might be able to suggest replacements (although > > not promising anything ...) > > This is the only discussion I can find: > > https://forum.polymake.org/viewtopic.php?t=1914 > > Let me remove that configure block and try to see what actually fails > when it builds ... The first error is: /home/rjones/d/fedora/polymake/rawhide/polymake-4.10/lib/core/src/perl/RefHash.xxs:737:11: error: ‘Perl_ck_fun’ was not declared in this scope; did you mean ‘Perl_cx_dup’? 737 |return Perl_ck_fun(aTHX_ o); | ^~~ | Perl_cx_dup ninja: build stopped: subcommand failed. As far as I can see that's the only missing / hidden Perl symbol. This symbol was hidden in: https://github.com/Perl/perl5/commit/0351a629e71de127cbfd1b142e9eaa6069deabf5 As for what it does, that's more tricky. I believe what it's doing is while Perl is parsing the input script, it is used to check that the thing you are calling is a function. Unfortunately it's slightly more complicated than that because it can convert some function-like things to functions (returning the updated OP*). Also Perl_ck_fun is complicated, to say the least: https://github.com/Perl/perl5/blob/a6d10131eee6ee336e4bd63f22a378e9d5ae40bd/op.c#L12522 For these reasons we can't just replace 'return Perl_ck_fun(aTHX_ o)' with 'return aTHX_ o', nor can be copy the function into the polymake source (since it calls other internal functions, but also for licensing reasons). So I think this does require upstream attention. Another note is this package requires ocaml-tplib which we orphaned. Rich. > > Rich. > > > > > Polymake upstream is aware of the issue. For the time being, they are > > > advising their downstreams to stay on perl 5.36.0, which is not > > > feasible for Fedora. In the long term, they plan to remove the > > > mandatory perl bindings from polymake. However, they as yet have no > > > timeline for that effort. It might be years. > > > > > > I don't see that I have any choice but to retire polymake from > > > Rawhide. This will have some repercussions: > > > - gap-pkg-polymaking, python-jupymake, and python-jupyter-polymake > > > will also be retired > > > - sagemath and Macaulay2 will be rebuilt without polymake support > > > - packages that I have maintained solely for use by polymake will be > > > orphaned: azove, permlib, plantri, sympol, vinci > > > > > > I could try begging the perl package maintainers to add a downstream > > > patch making the affected symbols visible again. However, since those > > > symbols are now internal only, the perl maintainers are free to alter > > > or remove them at any time, so that would not be a good long term > > > solution. > > > -- > > > Jerry James, who is currently channeling Billy Joel > > > http://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 > > > > -- > > 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 > > -- > Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones > Read my programming and virtualization blog: http://rwmj.wordpress.com >
[rpms/perl-Crypt-OpenSSL-PKCS10] PR #6: Fix build with Perl 5.38
mspacek closed without merging a pull-request against the project: `perl-Crypt-OpenSSL-PKCS10` that you are following. Closed pull-request: `` Fix build with Perl 5.38 `` https://src.fedoraproject.org/rpms/perl-Crypt-OpenSSL-PKCS10/pull-request/6 ___ 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-Crypt-OpenSSL-PKCS10] PR #6: Fix build with Perl 5.38
mspacek commented on the pull-request: `Fix build with Perl 5.38` that you are following: `` Heh, the same patch, ok :-) `` To reply, visit the link below https://src.fedoraproject.org/rpms/perl-Crypt-OpenSSL-PKCS10/pull-request/6 ___ 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
Fedora rawhide compose report: 20230718.n.0 changes
OLD: Fedora-Rawhide-20230717.n.0 NEW: Fedora-Rawhide-20230718.n.0 = SUMMARY = Added images:2 Dropped images: 3 Added packages: 4 Dropped packages:0 Upgraded packages: 372 Downgraded packages: 1 Size of added packages: 1.67 MiB Size of dropped packages:0 B Size of upgraded packages: 8.94 GiB Size of downgraded packages: 59.26 KiB Size change of upgraded packages: 1.19 MiB Size change of downgraded packages: -129 B = ADDED IMAGES = Image: Silverblue dvd-ostree aarch64 Path: Silverblue/aarch64/iso/Fedora-Silverblue-ostree-aarch64-Rawhide-20230718.n.0.iso Image: Workstation live aarch64 Path: Workstation/aarch64/iso/Fedora-Workstation-Live-aarch64-Rawhide-20230718.n.0.iso = DROPPED IMAGES = Image: Kinoite dvd-ostree aarch64 Path: Kinoite/aarch64/iso/Fedora-Kinoite-ostree-aarch64-Rawhide-20230717.n.0.iso Image: Onyx dvd-ostree x86_64 Path: Onyx/x86_64/iso/Fedora-Onyx-ostree-x86_64-Rawhide-20230717.n.0.iso Image: Silverblue dvd-ostree ppc64le Path: Silverblue/ppc64le/iso/Fedora-Silverblue-ostree-ppc64le-Rawhide-20230717.n.0.iso = ADDED PACKAGES = Package: ansible-collection-community-crypto-2.14.1-1.fc39 Summary: The community.crypto collection for Ansible RPMs:ansible-collection-community-crypto Size:248.13 KiB Package: golang-github-quic-0.36.2-1.20230716gitde8d7a3.fc39 Summary: A QUIC implementation in pure Go RPMs:golang-github-quic-devel Size:510.50 KiB Package: liboqs-0.8.0-1.fc39 Summary: liboqs is an open source C library for quantum-safe cryptographic algorithms. RPMs:liboqs liboqs-devel Size:756.60 KiB Package: rpm-head-signing-1.7.1-1.fc39 Summary: A python module for signing RPM header and file digests RPMs:rpm-head-signing Size:191.06 KiB = DROPPED PACKAGES = = UPGRADED PACKAGES = Package: Mars-4.5-22.fc39 Old package: Mars-4.5-21.fc38 Summary: An interactive development environment for programming in MIPS assembly language RPMs: Mars Size: 3.11 MiB Size change: -97 B Changelog: * Mon Jul 17 2023 W. Michael Petullo - 4.5-22 - Remove jpackage-utils requirement; it is retired and not needed Package: adwaita-icon-theme-45~beta-1.fc39 Old package: adwaita-icon-theme-44.0-1.fc39 Summary: Adwaita icon theme RPMs: adwaita-cursor-theme adwaita-icon-theme adwaita-icon-theme-devel Size: 2.33 MiB Size change: 637.07 KiB Changelog: * Sun Jul 16 2023 David King - 45~beta-1 - Update to 45.beta Package: akonadi-calendar-tools-23.04.3-1.fc39 Old package: akonadi-calendar-tools-23.04.2-1.fc39 Summary: Akonadi Calendar Tools RPMs: akonadi-calendar-tools Size: 930.72 KiB Size change: 6.97 KiB Changelog: * Sat Jul 08 2023 Marc Deop i Argem?? - 23.04.3-1 - 23.04.3 Package: akonadi-import-wizard-23.04.3-1.fc39 Old package: akonadi-import-wizard-23.04.2-1.fc39 Summary: Akonadi Import Wizard RPMs: akonadi-import-wizard akonadi-import-wizard-devel Size: 2.34 MiB Size change: 434 B Changelog: * Sat Jul 08 2023 Marc Deop i Argem?? - 23.04.3-1 - 23.04.3 Package: akonadiconsole-23.04.3-1.fc39 Old package: akonadiconsole-23.04.2-1.fc39 Summary: Akonadi developer tool RPMs: akonadiconsole Size: 1.51 MiB Size change: -131 B Changelog: * Sat Jul 08 2023 Marc Deop i Argem?? - 23.04.3-1 - 23.04.3 Package: akregator-23.04.3-1.fc39 Old package: akregator-23.04.2-1.fc39 Summary: Feed Reader RPMs: akregator akregator-libs Size: 5.83 MiB Size change: 2.02 KiB Changelog: * Sat Jul 08 2023 Marc Deop i Argem?? - 23.04.3-1 - 23.04.3 Package: alligator-23.04.3-1.fc39 Old package: alligator-23.04.2-1.fc39 Summary: Kirigami-based RSS reader RPMs: alligator Size: 641.74 KiB Size change: 4.65 KiB Changelog: * Sat Jul 08 2023 Marc Deop i Argem?? - 23.04.3-1 - 23.04.3 Package: analitza-23.04.3-1.fc39 Old package: analitza-23.04.2-1.fc39 Summary: Library of mathematical features RPMs: analitza analitza-devel Size: 3.02 MiB Size change: 260 B Changelog: * Sat Jul 08 2023 Marc Deop i Argem?? - 23.04.3-1 - 23.04.3 Package: angelfish-23.04.3-1.fc39 Old package: angelfish-23.04.2-1.fc39 Summary: Plasma Mobile minimal web browser RPMs: angelfish Size: 714.23 KiB Size change: 610 B Changelog: * Sat Jul 08 2023 Marc Deop i Argem?? - 23.04.3-1 - 23.04.3 Package: ark-23.04.3-1.fc39 Old package: ark-23.04.2-1.fc39 Summary: Archive manager RPMs: ark ark-libs Size: 6.99 MiB Size change: 153 B Changelog: * Sat Jul 08 2023 Marc Deop i Argem?? - 23.04.3-1 - 23.04.3 Package: artikulate-23.04.3-1.fc39 Old package: artikulate-23.04.2-1.fc39 Summary: Improve your pronunciation by listening to native speakers RPMs: artikulate artikulate-libs Size: 5.25 MiB Size change
Re: fedora-review workarounds for dnf5
Hello Jerry,
I proposed a workaround a few days ago
https://pagure.io/FedoraReview/pull-request/485
but your patch looks like a proper fix. I'll try it and merge to the
fedora-review codebase.
Does anybody know what was the purpose of --resolve and if it will be
no problem when we remove it?
Jakub
On Tue, Jul 18, 2023 at 12:39 AM Sandro wrote:
>
> On 17-07-2023 20:39, Jerry James wrote:
> > On Mon, Jul 17, 2023 at 10:54 AM Jerry James wrote:
> >> Like many of you, I have been quite inconvenienced because of
> >> dnf5-related breakage of fedora-review. I've been monkeying with it
> >> today and finally got a successful run of fedora-review after making
> >> the following changes [*].
> >>
> >> 1. Edit /etc/mock/templates/fedora-rawhide.tpl. Change:
> >>
> >> config_opts['package_manager'] = 'dnf'
> >>
> >> to:
> >>
> >> config_opts['package_manager'] = 'dnf5'
> >>
> >> 2. Run 'mock -r fedora-rawhide-x86_64 --scrub=bootstrap'
> >>
> >> 3. Edit /usr/lib/python3.11/site-packages/FedoraReview/deps.py. Change
> >> line
> >> 83 from:
> >>
> >> "dnf repoquery -q -C --requires --resolve " + "
> >> ".join(list(set(pkgs))),
> >>
> >> to:
> >>
> >> "dnf repoquery -q -C --requires " + " ".join(list(set(pkgs))),
> >>
> >> Change line 97 from:
> >>
> >> name = line.rsplit(".", 2)[0]
> >>
> >> to:
> >>
> >> name = resolve_one(line)[0].rsplit(".", 2)[0]
> >>
> >> Change line 286 from:
> >>
> >> "dnf repoquery -C -l " + " ".join(list(set(pkgs))),
> >>
> >> to:
> >>
> >> "dnf repoquery --files " + " ".join(list(set(pkgs))),
> >>
> >> Other changes may be needed.
> >>
> >> [*] Altering rpm-controlled files is generally a bad idea, and I do not
> >> recommend it. I am only doing so in this case because fedora-review
> >> does
> >> not work at all without these changes. I understand that my changes
> >> will
> >> be overwritten the next time a mock-core-configs or fedora-review
> >> update
> >> is installed.
> >
> > Skip steps 1 and 2. They are unnecessary. Step 3 is all you need.
>
> Would that be a temporary solution for Copr as well? I mean for all
> rawhide builds? I quite miss not having fedora-review available there.
>
> -- Sandro
> ___
> 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: RFC: Roadmap for DNF5 in Fedora 39 / invoking the Contingency Mechanism
> On 7/13/23 23:59, Fabio Valentini wrote: > > +1 for postponing. We have hit issues preparing CI environment via > ansible and applying workarounds to make dnf5 work is imho not the way > to go with such core tool. It should be there as opt-in so it can get > tested but not default. The problem is that ansible uses a different release cycle then Fedora. DNF5 is already in Fedora 38 and not only for testing, but also as a replacement of microdnf. Please check the list of reported issue and you will find that a lot of issues are currently resolved. 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: RFC: Roadmap for DNF5 in Fedora 39 / invoking the Contingency Mechanism
Hello, > We keep the list of issues tracked here: > https://github.com/rpm-software-management/mock/issues/894 > And namely, https://github.com/rpm-software-management/dnf5/issues/617 > seems like a showstopper ATM. At least as long as we have to check > GPG signatures at koji buildroot installation time. The issue https://github.com/rpm-software-management/dnf5/issues/617 is under development and we will handle it as a priority issue. 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: fedora-scm-requests email
That's strange, I never noticed this e-mail when doing initial testing during first deployment on production. Michal On 18. 07. 23 5:35, Kevin Fenzi wrote: On Tue, Jul 18, 2023 at 02:37:54AM +, Maxwell G wrote: Hi, It seems the fedora-scm-requests processor is creating the initial repository commits with `releng bot ` as the committer. Does anyone know where this is coming from? Should it be changed to something @fedoraproject.org? Very strange. I fixed it in the db... but I am not sure what caused it. Can look more tomorrow... it looks like it may have been this way since the automated processing started. ;( 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: Say goodbye to polymake
On Tue, Jul 18, 2023 at 08:23:54AM +0100, Richard W.M. Jones wrote: > On Mon, Jul 17, 2023 at 04:13:59PM -0600, Jerry James wrote: > > The introduction of perl 5.38.0 broke polymake beyond repair. Several > > symbols formerly used by polymake have been marked as internal APIs. > > They now have the ELF hidden attribute, so we can't even cheat by > > adding prototypes to the polymake code. > > Do you have a list of the deprecated APIs they are using? Or a link > to a bug on the topic? I happen to have far too much experience of > Perl internals and I might be able to suggest replacements (although > not promising anything ...) This is the only discussion I can find: https://forum.polymake.org/viewtopic.php?t=1914 Let me remove that configure block and try to see what actually fails when it builds ... > Rich. > > > Polymake upstream is aware of the issue. For the time being, they are > > advising their downstreams to stay on perl 5.36.0, which is not > > feasible for Fedora. In the long term, they plan to remove the > > mandatory perl bindings from polymake. However, they as yet have no > > timeline for that effort. It might be years. > > > > I don't see that I have any choice but to retire polymake from > > Rawhide. This will have some repercussions: > > - gap-pkg-polymaking, python-jupymake, and python-jupyter-polymake > > will also be retired > > - sagemath and Macaulay2 will be rebuilt without polymake support > > - packages that I have maintained solely for use by polymake will be > > orphaned: azove, permlib, plantri, sympol, vinci > > > > I could try begging the perl package maintainers to add a downstream > > patch making the affected symbols visible again. However, since those > > symbols are now internal only, the perl maintainers are free to alter > > or remove them at any time, so that would not be a good long term > > solution. > > -- > > Jerry James, who is currently channeling Billy Joel > > http://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 > > -- > 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 -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 100 libraries supported. http://fedoraproject.org/wiki/MinGW ___ 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: Say goodbye to polymake
On Mon, Jul 17, 2023 at 04:13:59PM -0600, Jerry James wrote: > The introduction of perl 5.38.0 broke polymake beyond repair. Several > symbols formerly used by polymake have been marked as internal APIs. > They now have the ELF hidden attribute, so we can't even cheat by > adding prototypes to the polymake code. Do you have a list of the deprecated APIs they are using? Or a link to a bug on the topic? I happen to have far too much experience of Perl internals and I might be able to suggest replacements (although not promising anything ...) Rich. > Polymake upstream is aware of the issue. For the time being, they are > advising their downstreams to stay on perl 5.36.0, which is not > feasible for Fedora. In the long term, they plan to remove the > mandatory perl bindings from polymake. However, they as yet have no > timeline for that effort. It might be years. > > I don't see that I have any choice but to retire polymake from > Rawhide. This will have some repercussions: > - gap-pkg-polymaking, python-jupymake, and python-jupyter-polymake > will also be retired > - sagemath and Macaulay2 will be rebuilt without polymake support > - packages that I have maintained solely for use by polymake will be > orphaned: azove, permlib, plantri, sympol, vinci > > I could try begging the perl package maintainers to add a downstream > patch making the affected symbols visible again. However, since those > symbols are now internal only, the perl maintainers are free to alter > or remove them at any time, so that would not be a good long term > solution. > -- > Jerry James, who is currently channeling Billy Joel > http://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 -- 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
[Bug 2223434] perl-Crypt-OpenSSL-PKCS10-0.20 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2223434 Jitka Plesnikova changed: What|Removed |Added Blocks||635 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=635 [Bug 635] F39FailsToInstall: perl-Crypt-OpenSSL-PKCS10 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2223434 ___ 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 2222635] F39FailsToInstall: perl-Crypt-OpenSSL-PKCS10
https://bugzilla.redhat.com/show_bug.cgi?id=635 Jitka Plesnikova changed: What|Removed |Added Depends On||2223434 CC||jples...@redhat.com Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=2223434 [Bug 2223434] perl-Crypt-OpenSSL-PKCS10-0.20 is available -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=635 ___ 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 2184301] perl-Syntax-Feature-Loop-1.8.0-18.fc39 FTBFS: t/01_basic.t and 3 more tests fail
https://bugzilla.redhat.com/show_bug.cgi?id=2184301 Jitka Plesnikova changed: What|Removed |Added Blocks||2168842 ||(F39FTBFS,RAWHIDEFTBFS) Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=2168842 [Bug 2168842] Fedora 39 FTBFS Tracker -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2184301 ___ 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 2223530] perl-MooseX-App: FTBFS with Perl 5.38
https://bugzilla.redhat.com/show_bug.cgi?id=2223530 Jitka Plesnikova changed: What|Removed |Added Blocks||2168842 ||(F39FTBFS,RAWHIDEFTBFS) Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=2168842 [Bug 2168842] Fedora 39 FTBFS Tracker -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2223530 ___ 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 2223530] perl-MooseX-App: FTBFS with Perl 5.38
https://bugzilla.redhat.com/show_bug.cgi?id=2223530 Jitka Plesnikova changed: What|Removed |Added Link ID||Github ||maros/MooseX-App/issues/69 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2223530 ___ 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: Orphaned libdnf-plugin-swidtags, planning to orphan swid-tools
On Tue, Jul 11, 2023 at 04:27:34PM +0200, Jan Pazdziora wrote: > > Hello, > > the SWID tag enablement introduced by > https://fedoraproject.org/wiki/Changes/SWID_Tag_Enablement did not lead > to a wider SWID tag adoption, and other technologies (IMA, SPDX) seem > to be more relevant for the purpose SWID tags were expected to play, > four years later. > > For that reason I've orphaned libdnf-plugin-swidtags. > > I'm looking for ways to reach out to the rpm-software-management-sig > who are co-maintainers of https://src.fedoraproject.org/rpms/swid-tools > to see what their interest / plang might be about swid-tools but > overall I'm leaning towards orphaning swid-tools as well shortly. I've now orphaned swid-tools in Fedora as well. -- Jan Pazdziora | Sr. Principal Software Engineer | Red Hat ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2223530] New: perl-MooseX-App: FTBFS with Perl 5.38
https://bugzilla.redhat.com/show_bug.cgi?id=2223530
Bug ID: 2223530
Summary: perl-MooseX-App: FTBFS with Perl 5.38
Product: Fedora
Version: rawhide
URL: https://koschei.fedoraproject.org/package/perl-MooseX-
App
OS: Linux
Status: NEW
Component: perl-MooseX-App
Severity: medium
Assignee: emman...@seyman.fr
Reporter: jples...@redhat.com
QA Contact: extras...@fedoraproject.org
CC: emman...@seyman.fr, jples...@redhat.com,
perl-devel@lists.fedoraproject.org
Target Milestone: ---
Classification: Fedora
Description of problem:
Package perl-MooseX-App fails to build from source with Perl 5.38 in Fedora
Rawhide.
Smartmatch is deprecated at
/builddir/build/BUILD/MooseX-App-1.42/blib/lib/MooseX/App/Meta/Role/Class/Base.pm
line 741.
# Failed test 'no warnings'
# at /usr/share/perl5/vendor_perl/Test/Builder.pm line 193.
# There were 24 warning(s)
# Previous test 0 ''
# given is deprecated at
/builddir/build/BUILD/MooseX-App-1.42/blib/lib/MooseX/App/Utils.pm line 237.
# at /builddir/build/BUILD/MooseX-App-1.42/blib/lib/MooseX/App/Utils.pm line
237.
# require MooseX/App/Utils.pm called at
/builddir/build/BUILD/MooseX-App-1.42/blib/lib/MooseX/App/Exporter.pm line 11
# MooseX::App::Exporter::BEGIN() called at
/builddir/build/BUILD/MooseX-App-1.42/blib/lib/MooseX/App/Exporter.pm line 11
# eval {...} called at
/builddir/build/BUILD/MooseX-App-1.42/blib/lib/MooseX/App/Exporter.pm line 11
# require MooseX/App/Exporter.pm called at
/builddir/build/BUILD/MooseX-App-1.42/blib/lib/MooseX/App.pm line 14
# MooseX::App::BEGIN() called at
/builddir/build/BUILD/MooseX-App-1.42/blib/lib/MooseX/App.pm line 14
# eval {...} called at
/builddir/build/BUILD/MooseX-App-1.42/blib/lib/MooseX/App.pm line 14
# require MooseX/App.pm called at t/testlib/Test01.pm line 4
# Test01::BEGIN() called at t/testlib/Test01.pm line 4
# eval {...} called at t/testlib/Test01.pm line 4
# require Test01.pm called at t/01_basic.t line 11
# main::BEGIN() called at t/01_basic.t line 11
# eval {...} called at t/01_basic.t line 11
#
# --
# Previous test 0 ''
# when is deprecated at
/builddir/build/BUILD/MooseX-App-1.42/blib/lib/MooseX/App/Utils.pm line 238.
# at /builddir/build/BUILD/MooseX-App-1.42/blib/lib/MooseX/App/Utils.pm line
238.
# require MooseX/App/Utils.pm called at
/builddir/build/BUILD/MooseX-App-1.42/blib/lib/MooseX/App/Exporter.pm line 11
# MooseX::App::Exporter::BEGIN() called at
/builddir/build/BUILD/MooseX-App-1.42/blib/lib/MooseX/App/Exporter.pm line 11
# eval {...} called at
/builddir/build/BUILD/MooseX-App-1.42/blib/lib/MooseX/App/Exporter.pm line 11
# require MooseX/App/Exporter.pm called at
/builddir/build/BUILD/MooseX-App-1.42/blib/lib/MooseX/App.pm line 14
# MooseX::App::BEGIN() called at
/builddir/build/BUILD/MooseX-App-1.42/blib/lib/MooseX/App.pm line 14
# eval {...} called at
/builddir/build/BUILD/MooseX-App-1.42/blib/lib/MooseX/App.pm line 14
# require MooseX/App.pm called at t/testlib/Test01.pm line 4
# Test01::BEGIN() called at t/testlib/Test01.pm line 4
# eval {...} called at t/testlib/Test01.pm line 4
# require Test01.pm called at t/01_basic.t line 11
# main::BEGIN() called at t/01_basic.t line 11
# eval {...} called at t/01_basic.t line 11
#
Version-Release number of selected component (if applicable):
1.42-5.fc38
Steps to Reproduce:
koji build --scratch f39 perl-MooseX-App-1.42-5.fc38.src.rpm
Additional info:
This package is tracked by Koschei. See:
https://koschei.fedoraproject.org/package/perl-MooseX-App
Reproducible: Always
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2223530
Report this comment as SPAM:
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202223530%23c0
___
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
Orphaned python-testing.postgresql
I orphaned https://src.fedoraproject.org/rpms/python-testing.postgresql I do not use it any more. Feel free to grab it. -- Miroslav Suchy, RHCA Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys ___ 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-Crypt-OpenSSL-PKCS10] PR #6: Fix build with Perl 5.38
jplesnik commented on the pull-request: `Fix build with Perl 5.38` that you are following: `` New version 0.20 [1] appears with the fix was released. It would be better than patch. https://bugzilla.redhat.com/show_bug.cgi?id=2223434 `` To reply, visit the link below https://src.fedoraproject.org/rpms/perl-Crypt-OpenSSL-PKCS10/pull-request/6 ___ 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 2222638] F39FailsToInstall: perl-Tk
https://bugzilla.redhat.com/show_bug.cgi?id=638 Jitka Plesnikova changed: What|Removed |Added Blocks||639 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=639 [Bug 639] F39FailsToInstall: perl-Tk-TableMatrix -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=638 ___ 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 2222639] F39FailsToInstall: perl-Tk-TableMatrix
https://bugzilla.redhat.com/show_bug.cgi?id=639 Jitka Plesnikova changed: What|Removed |Added CC||jples...@redhat.com Doc Type|--- |If docs needed, set a value Resolution|--- |RAWHIDE Fixed In Version||perl-Tk-TableMatrix-1.29-3. ||fc39 Depends On||638 Status|NEW |CLOSED Last Closed||2023-07-18 06:17:14 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=638 [Bug 638] F39FailsToInstall: perl-Tk -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=639 ___ 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
