[Bug 2263711] New: perl-Business-ISMN-1.204 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2263711 Bug ID: 2263711 Summary: perl-Business-ISMN-1.204 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Business-ISMN 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: 1.204 Upstream release that is considered latest: 1.204 Current version/release in rawhide: 1.203-4.fc40 URL: http://search.cpan.org/dist/Business-ISMN 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/5433/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/perl-Business-ISMN -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2263711 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202263711%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 2263711] perl-Business-ISMN-1.204 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2263711 --- Comment #1 from Upstream Release Monitoring --- Scratch build failed. Details below: BuilderException: Build failed: Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-zhouql26/perl-Business-ISMN.spec']' returned non-zero exit status 1. StdOut: setting SOURCE_DATE_EPOCH=1707609600 error: Bad file: ./Business-ISMN-1.204.tar.gz: No such file or directory RPM build errors: Bad file: ./Business-ISMN-1.204.tar.gz: No such file or directory Traceback: File "/usr/local/lib/python3.11/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.11/site-packages/hotness/builders/koji.py", line 229, in build raise BuilderException( If you think this issue is caused by some bug in the-new-hotness, please report it on the-new-hotness issue tracker: https://github.com/fedora-infra/the-new-hotness/issues -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2263711 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202263711%23c1 -- ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2263711] perl-Business-ISMN-1.204 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2263711 --- Comment #2 from Upstream Release Monitoring --- Created attachment 2016295 --> https://bugzilla.redhat.com/attachment.cgi?id=2016295=edit Update to 1.204 (#2263711) -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2263711 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202263711%23c2 -- ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Regaining Packager Status
I have regained packager status and submitted a fresh review request for unretitement of the new version of fbf-mukti-fonts https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2263710 Hope to get it reviewed and unretired On Saturday, 27 January, 2024 at 10:28:24 am IST, Benson Muite wrote: Hi Anirban, On 26/01/2024 08.13, Anirban Mitra via devel wrote: > I want to retake fbf-mukti-fonts and uniol-fonts of which i am the upstream > developer. I have lost my membership in packager group and I could not log in > the pkg maintenance systtem > Please see: https://docs.fedoraproject.org/en-US/fesco/Policy_for_inactive_packagers/#returning You will need to open a ticket at https://pagure.io/packager-sponsors/new_issue/ and reconfirm your identity. Once done am happy to review the packages. Please create tickets in Bugzilla. -- ___ 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: just to let you know FESCo agreed to a preliminary injunction while we consider this issue
Am 10.02.24 um 09:47 schrieb Neal Gompa: Technically, turning off display sync completely is quite difficult right now since the actual driver stack in Linux underneath everything (both Wayland and X11) uses implicit sync right now (Linux kernel drivers, Mesa drivers, etc.). Interesting considering that I once read (but haven't fact check) that the Vulkan spec explicitly requires explicit sync instead of implicit, even if you for parts of it. That said, there's a move to support explicit sync in Wayland[1], and the first steps of that for KWin have been written up as a merge request[2]. Once there's an agreed upon mechanism for explicit sync, it would be possible to support something like that. [1]:https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/90 [2]:https://invent.kde.org/plasma/kwin/-/merge_requests/4800 Interesting read. I will just hope that this won't be something which ends up in "noone actually still looks at it"-land as some things sometimes end up in because people focused on different things and then forgot about it (well, kind natural for volunteer projects I guess). Kilian Hanich -- ___ 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 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 --- Comment #5 from Fedora Release Engineering --- Dear Maintainer, your package has an open Fails To Build From Source bug for Fedora 39. Action is required from you. If you can fix your package to build, perform a build in koji, and either create an update in bodhi, or close this bug without creating an update, if updating is not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to acknowledge this. If you have already fixed this issue, please close this Bugzilla report. Following the policy for such packages [2], your package will be orphaned if this bug remains in NEW state more than 8 weeks (not sooner than 2023-05-30). A week before the mass branching of Fedora 40 according to the schedule [3], any packages not successfully rebuilt at least on Fedora 38 will be retired regardless of the status of this bug. [1] https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ [2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ [3] https://fedorapeople.org/groups/schedule/f-40/f-40-key-tasks.html -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2184301 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202184301%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
[Test-Announce] Fedora 40 Rawhide 20240210.n.1 nightly compose nominated for testing
Announcing the creation of a new nightly release validation test event for Fedora 40 Rawhide 20240210.n.1. Please help run some tests for this nightly compose if you have time. For more information on nightly release validation testing, see: https://fedoraproject.org/wiki/QA:Release_validation_test_plan Notable package version changes: anaconda - 20240207.n.0: anaconda-40.20-1.fc40.src, 20240210.n.1: anaconda-40.21-2.fc40.src Test coverage information for the current release can be seen at: https://openqa.fedoraproject.org/testcase_stats/40 You can see all results, find testing instructions and image download locations, and enter results on the Summary page: https://fedoraproject.org/wiki/Test_Results:Fedora_40_Rawhide_20240210.n.1_Summary The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora_40_Rawhide_20240210.n.1_Installation https://fedoraproject.org/wiki/Test_Results:Fedora_40_Rawhide_20240210.n.1_Base https://fedoraproject.org/wiki/Test_Results:Fedora_40_Rawhide_20240210.n.1_Server https://fedoraproject.org/wiki/Test_Results:Fedora_40_Rawhide_20240210.n.1_Cloud https://fedoraproject.org/wiki/Test_Results:Fedora_40_Rawhide_20240210.n.1_Desktop https://fedoraproject.org/wiki/Test_Results:Fedora_40_Rawhide_20240210.n.1_Security_Lab Thank you for testing! -- Mail generated by relvalconsumer: https://pagure.io/fedora-qa/relvalconsumer -- ___ test-announce mailing list -- test-annou...@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2263687] New: perl-Business-ISBN-3.009 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2263687 Bug ID: 2263687 Summary: perl-Business-ISBN-3.009 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Business-ISBN 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, perl-devel@lists.fedoraproject.org Target Milestone: --- Classification: Fedora Releases retrieved: 3.009 Upstream release that is considered latest: 3.009 Current version/release in rawhide: 3.008-4.fc40 URL: https://metacpan.org/dist/Business-ISBN/ 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/2673/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/perl-Business-ISBN -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2263687 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202263687%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
Re: Unresponsive maintainer: petersen / Pandoc package not updated since June 2023: Security vulnerability, CVE-2023-35936 (medium)
On 09/02/2024 16.26, Jens-Ulrik Petersen wrote: I should also have added there's an increasing amount of technical debt with the pandoc packaging - I guess I need to beg people to help with package reviews: also reminded of our packaging (review) streamlining discussion from Flock last year. Jens Unfortunately, I couldn't attend last Flock, so I don't know the related discussion. But I will have a look on the current review guidelines in the next days, in order to check if this is a commitment I can reliably provide over time. Maybe I can support with this. I'll let you know if so. On Fri, 9 Feb 2024, 23:23 Jens-Ulrik Petersen, wrote: Hello I am here - thanks for contacting me. I was hoping to cover this as part of my F40 Change, but unfortunately I haven't gotten to it, so the Change is now at risk of being deferred to F41. Nevertheless I will see what I can do about this for F40: maybe a backport can also be done for F39. Next time you could also comment on the relevant bug: https://bugzilla.redhat.com/show_bug.cgi?id=1996301 - that would be appreciated. Thanks, Jens PS Special thanks to Neal Gompa for pinging me in Matrix. On Fri, 9 Feb 2024, 20:05 Christopher Klooz, wrote: I cannot reach the maintainer petersen (see mail below): The package "pandoc" remains at 3.1.3 in Fedora, but pandoc is already at 3.1.11.1. Among the updates since 3.1.3, there have been two security-critical (including the medium CVE-2023-35936. Security fixes are in 3.1.4 & 3.1.6). The actual risk is limited, but these should be updated nevertheless. Does anyone know how to reach him by other means? Regards, Chris Forwarded Message Subject: Fedora package "pandoc" outdated and contains security vulnerability Date: Thu, 1 Feb 2024 15:55:09 +0100 From: py0...@posteo.net To: peter...@fedoraproject.org Hi petersen, I am reaching out because of the package "pandoc", which you maintain. I have seen that the package is still at version 3.1.3 [1] when I tried to install it with dnf, whereas the current version is 3.1.11.1 [2]: is this intended or an accident? It has to be noted that the updates that have been added in the meantime contain fixes for security vulnerabilities (at least CVE-2023-35936; I have just roughly skimmed the changelogs). So at the moment, it seems the Fedora build can be exploited by attackers in some circumstances [3] [4] because it is still at 3.1.3. Regards & thanks for maintaining, Chris [1] https://koji.fedoraproject.org/koji/packageinfo?packageID=11560 [2] https://hackage.haskell.org/package/pandoc & https://github.com/jgm/pandoc [3] https://github.com/jgm/pandoc/releases?page=1 [4] https://github.com/jgm/pandoc/releases?page=2 -- ___ 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 -- ___ 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: Unresponsive maintainer: petersen / Pandoc package not updated since June 2023: Security vulnerability, CVE-2023-35936 (medium)
Hi Jens, Thanks for the information. Unfortunately, I didn't see the bugzilla ticket. On 09/02/2024 16.23, Jens-Ulrik Petersen wrote: Hello I am here - thanks for contacting me. I was hoping to cover this as part of my F40 Change, but unfortunately I haven't gotten to it, so the Change is now at risk of being deferred to F41. Nevertheless I will see what I can do about this for F40: maybe a backport can also be done for F39. Next time you could also comment on the relevant bug: https://bugzilla.redhat.com/show_bug.cgi?id=1996301 - that would be appreciated. Thanks, Jens PS Special thanks to Neal Gompa for pinging me in Matrix. On Fri, 9 Feb 2024, 20:05 Christopher Klooz, wrote: I cannot reach the maintainer petersen (see mail below): The package "pandoc" remains at 3.1.3 in Fedora, but pandoc is already at 3.1.11.1. Among the updates since 3.1.3, there have been two security-critical (including the medium CVE-2023-35936. Security fixes are in 3.1.4 & 3.1.6). The actual risk is limited, but these should be updated nevertheless. Does anyone know how to reach him by other means? Regards, Chris Forwarded Message Subject: Fedora package "pandoc" outdated and contains security vulnerability Date: Thu, 1 Feb 2024 15:55:09 +0100 From: py0...@posteo.net To: peter...@fedoraproject.org Hi petersen, I am reaching out because of the package "pandoc", which you maintain. I have seen that the package is still at version 3.1.3 [1] when I tried to install it with dnf, whereas the current version is 3.1.11.1 [2]: is this intended or an accident? It has to be noted that the updates that have been added in the meantime contain fixes for security vulnerabilities (at least CVE-2023-35936; I have just roughly skimmed the changelogs). So at the moment, it seems the Fedora build can be exploited by attackers in some circumstances [3] [4] because it is still at 3.1.3. Regards & thanks for maintaining, Chris [1] https://koji.fedoraproject.org/koji/packageinfo?packageID=11560 [2] https://hackage.haskell.org/package/pandoc & https://github.com/jgm/pandoc [3] https://github.com/jgm/pandoc/releases?page=1 [4] https://github.com/jgm/pandoc/releases?page=2 -- ___ 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
[Bug 2259172] perl-Tk-804.036-12.fc40 FTBFS: objGlue.c: In function ‘Tcl_GetByteArrayFromObj’: /usr/lib64/perl5/CORE/sv.h:1952:31: error: passing argument 3 of ‘Perl_SvPV_helper’ from incompatible poi
https://bugzilla.redhat.com/show_bug.cgi?id=2259172
Neil Hanlon changed:
What|Removed |Added
CC||n...@shrug.pw
--- Comment #1 from Neil Hanlon ---
I poked at this for a while -- the error I'm seeing now related to some Xlib
issue:
```
In file included from Xlib_f.c:17:
Xlib.t:334:1: warning: ‘XKeycodeToKeysym’ is deprecated
[-Wdeprecated-declarations]
334 | VFUNC(KeySym,XKeycodeToKeysym,V_XKeycodeToKeysym,_ANSI_ARGS_((Display
*, unsigned int, int)))
| ^
In file included from Xlib_f.c:4:
/usr/include/X11/Xlib.h:1687:15: note: declared here
1687 | extern KeySym XKeycodeToKeysym(
| ^~~~
Xlib.t:334:14: error: initialization of ‘KeySym (*)(Display *, unsigned int,
int)’ {aka ‘long unsigned int (*)(Display *, unsigned int, int)’} from
incompatible pointer type ‘KeySym (*)(Display *, KeyCode, int)’ {aka ‘long
unsigned int (*)(Display *, unsigned char, int)’}
[-Wincompatible-pointer-types]
334 | VFUNC(KeySym,XKeycodeToKeysym,V_XKeycodeToKeysym,_ANSI_ARGS_((Display
*, unsigned int, int)))
| ^~~~
Xlib_f.c:15:35: note: in definition of macro ‘VFUNC’
15 | #define VFUNC(type,name,mem,args) name,
| ^~~~
Xlib.t:334:14: note: (near initialization for ‘XlibVtable.V_XKeycodeToKeysym’)
334 | VFUNC(KeySym,XKeycodeToKeysym,V_XKeycodeToKeysym,_ANSI_ARGS_((Display
*, unsigned int, int)))
| ^~~~
Xlib_f.c:15:35: note: in definition of macro ‘VFUNC’
15 | #define VFUNC(type,name,mem,args) name,
| ^~~~
make[1]: *** [Makefile:861: Xlib_f.o] Error 1
```
I did find https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271521 which seems
similar, but that patch only reveals other errors for the Fedora build (I
think). I also tried changing it to an unsigned char, as it suggests, but this
causes issues elsewhere due to that assertion.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2259172
Report this comment as SPAM:
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202259172%23c1
--
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue
W dniu 9.02.2024 o 20:25, Roy Bekken pisze: I just booted Fedora-KDE-Live-x86_64-Rawhide-20240207.n.0.iso First impression is great but I’ll start moving(fast) the welcome center window around and the desktop randomly freezes from 30sec to 90ses. This is on a 1080 with nouveau, im not sure if its better with the proprietary drivers. NVidia 10xx is the worst option for nouveau. It is too new to have reclocking support (NVidia never released blobs/code for it for this generation). And it is too old to use new GSP based approach where you run tens of megabytes of blob and use nouveau on top of it. For 1080 the only option is proprietary driver. With all problems it generates. I had 1050 Ti. Sold it, moved to Radeon 6700 XT. Wayland works, X11 works, Cyberpunk 2077 works (both under Linux and Windows). -- ___ 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 2261446] perl-Cairo: FTBFS in Fedora rawhide/f40
https://bugzilla.redhat.com/show_bug.cgi?id=2261446 Tom "spot" Callaway changed: What|Removed |Added Status|NEW |CLOSED Doc Type|--- |If docs needed, set a value Resolution|--- |RAWHIDE Last Closed||2024-02-10 18:08:03 --- Comment #4 from Tom "spot" Callaway --- Fixed in perl-Cairo-1.109-13.fc40 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2261446 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202261446%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
Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue
On Saturday, 10 February 2024 01:11:03 CET Kevin Kofler via devel wrote: > By the way, what that link does not mention when it talks about "multiple > packages for the same thing" is browsers / web engines. The Spin ships > several applications using QtWebEngine, e.g., KMail, so that engine is not > going away. But in addition to one or two browsers using that, which add > little to no overhead size-wise, it still ships the duplicate application > Firefox that bundles its own, completely different web engine. See: > https://bugzilla.redhat.com/show_bug.cgi?id=1920298 . (The main argument has > always been market share, which at 2% market share and steadily decreasing > does not sound relevant anymore.) Let's stay on topic. Thanks. -- ___ 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: just to let you know FESCo agreed to a preliminary injunction while we consider this issue
On Fri, Feb 9, 2024 at 9:10 PM Kilian Hanich via devel wrote: > > > > Am 09.02.24 um 18:28 schrieb Neal Gompa: > > On Fri, Feb 9, 2024 at 12:16 PM Roy Bekken wrote: > >> > >> On fredag 9. februar 2024 17:41:33 CET Neal Gompa wrote: > >>> On Fri, Feb 9, 2024 at 11:06 AM Roy Bekken wrote: > >>> > > > On fredag 9. februar 2024 04:04:04 CET Steve Cossette wrote: > > > I am not gonna reply to all of that because all we are doing at this > > point > > is repeating the same thing. But we are NOT stopping you from using > > x11. > > You can either build it yourself and put it on a copr (it’s not like > > neal > > is using voodoo in his copr), use the copr we provide or … > > > > > > This is extremely hostile towards new people trying linux for the very > first time, asking them to add a copr repo if they have problems with > wayland to try X11, its unlikely they ever heard this stuff before. > > > > Most likely they are trying out Fedora on a live media. > > > >>> > >>> > >>> And they're not going to get an X11 experience on live media even now. > >>> Wayland has been used for all environment modes since Fedora 36. > >> I am aware if this. So you are saying that its perfectly fine that someone > >> new > >> to linux boot into a desktop that microstutters when they move windows > >> around? > > > > No, it's not fine. Just like it's not fine to get random > > tear/corruption snow when moving things around or opening windows on > > X11. > > > > The difference is that we can actually do something about those issues > > with Plasma Wayland when people report them. *Tons* of these kinds of > > issues were fixed over the past 3 years, and Plasma 6 brings a huge > > upgrade around this stuff too. And the whole graphics pipeline is > > fully under the control of KDE Plasma, so we can do things we've never > > done before. That's why we can do VRR, HDR, VR, mixed-DPI, fractional > > scaling, and so much more. > > > > We can do things that even other Wayland desktops can't do because our > > architecture is flexible enough to do it. With Plasma X11, our necks > > are hanging to the dying albatross that is the X server and our hands > > are tied behind our backs when we want to actually do something to > > improve the experience. These are not issues with Plasma Wayland. > > > > Because Plasma Wayland... is just KDE Plasma. > > > > > > > > Quite a bit of topic from my part, but is your pipeline for Wayland > flexible enough to turn off any kind of display sync (even in windowed > mode) if the user wants that? > > Sure, it has its downside (e.g. tearing can happen), but I rather have > that than the added latency (even if very minimal) of such a sync (and > yes, that includes VRR which has a considerable smaller one than normal > V-SYNC). Technically, turning off display sync completely is quite difficult right now since the actual driver stack in Linux underneath everything (both Wayland and X11) uses implicit sync right now (Linux kernel drivers, Mesa drivers, etc.). That said, there's a move to support explicit sync in Wayland[1], and the first steps of that for KWin have been written up as a merge request[2]. Once there's an agreed upon mechanism for explicit sync, it would be possible to support something like that. [1]: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/90 [2]: https://invent.kde.org/plasma/kwin/-/merge_requests/4800 -- 真実はいつも一つ！/ 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: exiv2 and protobuf hard to do soname bump without turbulence
On Sat, Feb 10, 2024, 01:50 Sérgio Basto wrote: > "In order to update Exiv2, we need to know if this is okay to enable > BMFF support. Patents have theorically expired and it is enabled by > default in the latest version." > > until isn't clear by legal it should be disabled , if default is enable > ,we should disable it and move on , it is not a show stopper > The problem in these cases is that if something has a chance that it's not legally all right, it also needs to be removed from the source code, disabling it just for the build isn't enough. > -- ___ 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
