[EPEL-devel] Re: Nemo for EPEL8?
Hi Pat, On Fri, Jul 16, 2021 at 03:16:30PM -0500, Pat Riehecky wrote: > That sounds super neat! > > Last time I looked at what it would take for cinnamon on EPEL8 the > base desktop had a number of dependencies that weren't branched (sassc > being the one I remember right now). I think that may have been 2019 > though > > If you're interested in working on nemo in EPEL8, I've no objections, > but leigh123linux is the real voice here. Leigh has put a lot of work > into various bits of Cinnamon on Fedora over the years. > Note that I'm not looking at building the whole Cinnamon (yet), cinnamon-desktop is actually just some shared libraries. Best regards, -- Michel Alexandre Salim profile: https://keyoxide.org/mic...@michel-slm.name signature.asc Description: PGP signature ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Fedora EPEL 7 updates-testing report
The following Fedora EPEL 7 Security updates need testing: Age URL 50 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-1f259a45ef openjpeg2-2.3.1-11.el7 5 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-ddb4fcb22a opendmarc-1.4.1.1-3.el7 The following builds have been pushed to Fedora EPEL 7 updates-testing lua-unbound-1.0.0-1.el7 procenv-0.60-1.el7 Details about builds: lua-unbound-1.0.0-1.el7 (FEDORA-EPEL-2021-acfd8bd292) Binding to libunbound for Lua Update Information: - Upgrade to 1.0.0 (#198) ChangeLog: * Fri Jul 16 2021 Robert Scheck 1.0.0-1 - Upgrade to 1.0.0 (#198) References: [ 1 ] Bug #198 - lua-unbound-1.0.0 is available https://bugzilla.redhat.com/show_bug.cgi?id=198 procenv-0.60-1.el7 (FEDORA-EPEL-2021-7dc76aa76e) Utility to show process environment Update Information: Update to 0.60 (minor features and fixes). ChangeLog: * Wed Jul 14 2021 Dave Love - 0.60-1 - New version * Tue Jul 13 2021 Dave Love - 0.58-1 - New version * Sat Jun 19 2021 Dave Love - 0.57-1 - New version * Tue Jun 8 2021 Dave Love - 0.55-1 - New version * Thu Mar 18 2021 Dave Love - 0.54-1 - New version - Drop patch * Wed Jan 27 2021 Fedora Release Engineering - 0.51-5 - Rebuilt for https://fedoraproject.org/wiki/Fedora_34_Mass_Rebuild * Wed Jan 6 2021 Dave Love - 0.51-5 - Fix error with gcc 10 with patch, not compiler flags - Use numactl on s390 * Tue Jul 28 2020 Fedora Release Engineering - 0.51-4 - Rebuilt for https://fedoraproject.org/wiki/Fedora_33_Mass_Rebuild * Mon Feb 17 2020 Dave love - 0.51-3 - Avoid FTBFS (#1799896) * Thu Jan 30 2020 Fedora Release Engineering - 0.51-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_32_Mass_Rebuild ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Fedora EPEL 8 updates-testing report
The following Fedora EPEL 8 Security updates need testing: Age URL 7 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-f971d08ec9 chromium-91.0.4472.114-2.el8 5 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-8f073f9e87 opendmarc-1.4.1.1-3.el8 4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-9ca0db533c kitty-0.19.3-1.el8 The following builds have been pushed to Fedora EPEL 8 updates-testing lua-unbound-1.0.0-1.el8 openjdk-asmtools-7.0.b10-0.2.20210610.gitf40a2c0.el8 procenv-0.60-1.el8 qpid-proton-0.35.0-1.el8 Details about builds: lua-unbound-1.0.0-1.el8 (FEDORA-EPEL-2021-f0020b5d2a) Binding to libunbound for Lua Update Information: - Upgrade to 1.0.0 (#198) ChangeLog: * Fri Jul 16 2021 Robert Scheck 1.0.0-1 - Upgrade to 1.0.0 (#198) References: [ 1 ] Bug #198 - lua-unbound-1.0.0 is available https://bugzilla.redhat.com/show_bug.cgi?id=198 openjdk-asmtools-7.0.b10-0.2.20210610.gitf40a2c0.el8 (FEDORA-EPEL-2021-744903fb46) To develop tools create proper & improper Java '.class' files Update Information: updated to latest sources ChangeLog: procenv-0.60-1.el8 (FEDORA-EPEL-2021-794c5ff148) Utility to show process environment Update Information: Update to 0.60 (minor features and fixes). ChangeLog: * Wed Jul 14 2021 Dave Love - 0.60-1 - New version * Tue Jul 13 2021 Dave Love - 0.58-1 - New version * Sat Jun 19 2021 Dave Love - 0.57-1 - New version * Tue Jun 8 2021 Dave Love - 0.55-1 - New version * Thu Mar 18 2021 Dave Love - 0.54-1 - New version - Drop patch * Wed Jan 27 2021 Fedora Release Engineering - 0.51-5 - Rebuilt for https://fedoraproject.org/wiki/Fedora_34_Mass_Rebuild * Wed Jan 6 2021 Dave Love - 0.51-5 - Fix error with gcc 10 with patch, not compiler flags - Use numactl on s390 * Tue Jul 28 2020 Fedora Release Engineering - 0.51-4 - Rebuilt for https://fedoraproject.org/wiki/Fedora_33_Mass_Rebuild * Mon Feb 17 2020 Dave love - 0.51-3 - Avoid FTBFS (#1799896) * Thu Jan 30 2020 Fedora Release Engineering - 0.51-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_32_Mass_Rebuild qpid-proton-0.35.0-1.el8 (FEDORA-EPEL-2021-5f8d9a62ef) A high performance, lightweight messaging library Update Information: Rebased to 0.35.0 ChangeLog: * Wed Jun 16 2021 Kim van der Riet - 0.35.0-1 - Rebased to 0.35.0 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Nemo for EPEL8?
Hi Leigh and Pat, (cc:ed epel-developers) I maintain the EPEL8 branch of nextcloud-client, and it has a subpackage, -nemo, that's currently uninstallable because Nemo is not built in EPEL8: https://bugzilla.redhat.com/show_bug.cgi?id=1982034 I checked the dependency trees, and Nemo and all the packages needed to built it (cinnamon-desktop and xapps) are actually already branched, but never released for EPEL8. nemo also has a runtime dependency on cinnamon-translations. The latest version of xapps I can build is 1.6.10 from the F31 branch (1.8 and above won't build), which limits the version of Nemo that builds (I've just been trawling the spec history, so this might not be 100% accurate) to 4.6.5 from the F32 branch. cinnamon-desktop's Rawhide branch rebuilds fine and I have not tried cinnamon-translations but I suspect it will be fine too. The question I have is... given all these packages are already branched, presumably at some point there was a plan to bring Cinnamon to EPEL8. - Is that no longer going to happen, and if so, why? - Are there concerns about having an older version of Nemo available in EPEL8 (especially when it comes to potential security issues)? I'm interested in file managers in general, and would not mind co-maintaining these set of four packages just to check them out, but if there are valid reasons why they are not available then I will just disable nextcloud-client-nemo when building on EL8. Thanks, -- Michel Alexandre Salim profile: https://keyoxide.org/mic...@michel-slm.name signature.asc Description: PGP signature ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Re: rpmautospec deployment into production
Hi Nils, On Fri, Jul 16, 2021 at 03:19:25PM +0200, Nils Philippsen wrote: > > in order to use rpmautospec features, it needs to be available on the > builder machines (which are F34) and, for local operations, on the > machine running fedpkg or equivalent. I.e. making it available on EL8 > will help people whose work environment is RHEL8 or CentOS 8, it > shouldn't be required to be able to build an EL8 package in our > infrastructure. There seems to be a bug[1] which prevents building EL8 > packages that use %autorelease, %autochangelog, which I'm investigating > right now. Huh, the EPEL8 builders are F34? I just realized. Yeah, fedpkg --release epel8 srpm definitely behaved differently on F34 (where the macros are available) and on EPEL8 (not on my EL8 machine now so can't get the exact message, but IIRC it failed saying the changelog was invalid). > > I'd be happy to be able to offer rpmautospec client-side on EL8, too, > but as you found out in [2], this needs a newer pygit2 version than > what is available there. > pygit2 is maintained in EPEL, so there's a possibility of just upgrading it there; I'll have to check if it might break any dependencies though. Would you happen to know what is the minimum pygit2 version that would work for rpmautospec? Thanks, -- Michel Alexandre Salim profile: https://keyoxide.org/mic...@michel-slm.name signature.asc Description: PGP signature ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: rpmautospec deployment into production
On 16. 07. 21 19:58, Robert-André Mauchin wrote: On 6/16/21 6:03 PM, Nils Philippsen wrote: Hi everybody, we've scheduled the rpmautospec plugin to be deployed into production for tomorrow, from 14:00 UTC on. This means installing the relevant packages and restarting kojid processes on the builders, which will restart any tasks which are being processed at that time, i.e. expect delays for builds in-flight at the time. We'll announce when the deployment is done. Cheers, Nils What is the situation wrt new packages? Should we enforce the use of rpmautospec during reviews or is it completely optional? It is completely optional. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Do we need Mock supported on EL7?
We touched this topic several times before in our team. Perhaps we should move on and do it... it would simplify a development (the yum/dnf hacks, legacy systemd-nspawn hacks, podman requirement for building Fedora, etc.). I created an issue [1], can you please vote there if you are concerned? If you have a good argument for keeping the support, please write here or there (or both). [1] https://github.com/rpm-software-management/mock/issues/755 Thank you, Pavel ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Do we need Mock supported on EL7?
We touched this topic several times before in our team. Perhaps we should move on and do it... it would simplify a development (the yum/dnf hacks, legacy systemd-nspawn hacks, podman requirement for building Fedora, etc.). I created an issue [1], can you please vote there if you are concerned? If you have a good argument for keeping the support, please write here or there (or both). [1] https://github.com/rpm-software-management/mock/issues/755 Thank you, Pavel ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Test-Announce] Proposal to CANCEL: 2021-07-19 Fedora QA Meeting
Hi folks! I'm proposing we cancel the QA meeting on Monday. I don't have anything urgent on the agenda, so let's take a break. If you're aware of anything important we have to discuss this week, please do reply to this mail and we can go ahead and run the meeting. Thanks! -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net ___ test-announce mailing list -- test-annou...@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Re: Nemo for EPEL8?
Hi Michal, Looking through the past emails on the list, it looks like the Cinnamon desktop people stopped maintaining it for epel, back around the time we were branching things for epel8. I think more than being a co-maintainer, that you would be the epel maintainer. https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/thread/3URMFE6D4AYY3B2PIS5KS6PVDJIADO2L/ https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/thread/UEWQ7LPFYGCHXAGKS3YK2YPCLBCCNDSQ/ On Fri, Jul 16, 2021 at 12:53 PM Michel Alexandre Salim < mic...@michel-slm.name> wrote: > Hi Leigh and Pat, > > (cc:ed epel-developers) > > I maintain the EPEL8 branch of nextcloud-client, and it has a > subpackage, -nemo, that's currently uninstallable because Nemo is not > built in EPEL8: > https://bugzilla.redhat.com/show_bug.cgi?id=1982034 > > I checked the dependency trees, and Nemo and all the packages needed to > built it (cinnamon-desktop and xapps) are actually already branched, but > never released for EPEL8. nemo also has a runtime dependency on > cinnamon-translations. > > The latest version of xapps I can build is 1.6.10 from the F31 branch > (1.8 and above won't build), which limits the version of Nemo that > builds (I've just been trawling the spec history, so this might not be > 100% accurate) to 4.6.5 from the F32 branch. cinnamon-desktop's Rawhide > branch rebuilds fine and I have not tried cinnamon-translations but I > suspect it will be fine too. > > The question I have is... given all these packages are already branched, > presumably at some point there was a plan to bring Cinnamon to EPEL8. > > - Is that no longer going to happen, and if so, why? > - Are there concerns about having an older version of Nemo available in > EPEL8 (especially when it comes to potential security issues)? > > I'm interested in file managers in general, and would not mind > co-maintaining these set of four packages just to check them out, but if > there are valid reasons why they are not available then I will just > disable nextcloud-client-nemo when building on EL8. > > Thanks, > > -- > Michel Alexandre Salim > profile: https://keyoxide.org/mic...@michel-slm.name > ___ > 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 on the list, report it: > https://pagure.io/fedora-infrastructure > ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: rpmautospec deployment into production
Hi Nils, On Fri, Jul 16, 2021 at 03:19:25PM +0200, Nils Philippsen wrote: > > in order to use rpmautospec features, it needs to be available on the > builder machines (which are F34) and, for local operations, on the > machine running fedpkg or equivalent. I.e. making it available on EL8 > will help people whose work environment is RHEL8 or CentOS 8, it > shouldn't be required to be able to build an EL8 package in our > infrastructure. There seems to be a bug[1] which prevents building EL8 > packages that use %autorelease, %autochangelog, which I'm investigating > right now. Huh, the EPEL8 builders are F34? I just realized. Yeah, fedpkg --release epel8 srpm definitely behaved differently on F34 (where the macros are available) and on EPEL8 (not on my EL8 machine now so can't get the exact message, but IIRC it failed saying the changelog was invalid). > > I'd be happy to be able to offer rpmautospec client-side on EL8, too, > but as you found out in [2], this needs a newer pygit2 version than > what is available there. > pygit2 is maintained in EPEL, so there's a possibility of just upgrading it there; I'll have to check if it might break any dependencies though. Would you happen to know what is the minimum pygit2 version that would work for rpmautospec? Thanks, -- Michel Alexandre Salim profile: https://keyoxide.org/mic...@michel-slm.name signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1983178] perl-IPC-Shareable-1.05 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1983178 --- Comment #1 from Upstream Release Monitoring --- An HTTP error occurred downloading the package's new Source URLs: Getting https://cpan.metacpan.org/authors/id/M/MS/MSOUTH/IPC-Shareable-1.05.tar.gz to ./IPC-Shareable-1.05.tar.gz -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1983178] New: perl-IPC-Shareable-1.05 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1983178 Bug ID: 1983178 Summary: perl-IPC-Shareable-1.05 is available Product: Fedora Version: rawhide Status: NEW Component: perl-IPC-Shareable Keywords: FutureFeature, Triaged Assignee: spo...@gmail.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: jose.p.oliveira@gmail.com, perl-devel@lists.fedoraproject.org, spo...@gmail.com Target Milestone: --- Classification: Fedora Latest upstream release: 1.05 Current version/release in rawhide: 1.04-1.fc35 URL: http://search.cpan.org/dist/IPC-Shareable Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/7130/ -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: rpmautospec deployment into production
On 6/16/21 6:03 PM, Nils Philippsen wrote: Hi everybody, we've scheduled the rpmautospec plugin to be deployed into production for tomorrow, from 14:00 UTC on. This means installing the relevant packages and restarting kojid processes on the builders, which will restart any tasks which are being processed at that time, i.e. expect delays for builds in-flight at the time. We'll announce when the deployment is done. Cheers, Nils What is the situation wrt new packages? Should we enforce the use of rpmautospec during reviews or is it completely optional? Best regards, Robert-André ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: building against epel8 modules
Btw, not sure who did what, but thanx a lot. Without any touches, the epel8 package now builds fine. So thank ou fedora relengs! J. On 6/22/21 6:27 PM, Jiri Vanek wrote: Hello! I have an ordinery package, which builds as is for epel7,and all fedoras, but not for epel8: Package openjdk-asmtools builds fine in fedora, epel7 and rhel8, but not in epel8: CentOS-8 - Extras 4.3 kB/s | 1.5 kB 00:00 Extra Packages for Enterprise Linux 8 - x86_64 75 kB/s | 4.7 kB 00:00 Error: Problem 1: conflicting requests - package maven-compiler-plugin-3.7.0-2.module_el8.0.0+30+832da3a1.noarch is filtered out by modular filtering Problem 2: conflicting requests - package maven-jar-plugin-3.1.0-1.module_el8.0.0+30+832da3a1.noarch is filtered out by modular filtering Problem 3: conflicting requests - package maven-local-5.3.0-2.module_el8.0.0+30+832da3a1.noarch is filtered out by modular filtering web search is failing me. Is there some magical spec switch which is enbaling... modules? or something? Thanx! j. -- Jiri Vanek Mgr. Principal QA Software Engineer Red Hat Inc. +420 775 39 01 09 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: building against epel8 modules
Yup. That sounds like a plan. On 7/2/21 11:52 AM, Vít Ondruch wrote: Dne 02. 07. 21 v 5:25 Nico Kadel-Garcia napsal(a): On Thu, Jul 1, 2021 at 11:24 PM Nico Kadel-Garcia wrote: On Thu, Jul 1, 2021 at 9:20 PM Josh Boyer wrote: On Wed, Jun 23, 2021, 4:58 AM Nico Kadel-Garcia wrote: On Tue, Jun 22, 2021 at 1:25 PM Jiri Vanek wrote: On 6/22/21 7:08 PM, Stephen John Smoogen wrote: Welcome to RHEL-8 modularity and the joy it brings anyone trying to port software to 8. The problem is not with EPEL but with the way hmm. Thanx a lot of for a bt of light in darknes.. or mayb emore darkness in twilight :-) I can't find *anyone* who likes modularity. I'm devoutly hoping that it is discarded for RHEL 9. For the record, it is not being discarded in RHEL 9. josh Any chance of ignoring it almost entirely, or only using it for modular packages? It caused real dependency for some perl modules, and even the name is confusing when we start talking about perl and python modules. Sorry, I meant "only use it for entirely optional, non-build-related software". The initial versions of SW will be (mostly) non-modular, additional versions will be (mostly) modular. Vít ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure -- Jiri Vanek Mgr. Principal QA Software Engineer Red Hat Inc. +420 775 39 01 09 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: [Fedocal] Reminder meeting : ELN SIG
On Fri, Jul 16, 2021 at 10:59 AM Troy Dawson wrote: > > This might not warrant a meeting, but it's something that just came up. > ELN-Extra > I never went beyond the Content Resolver initial setup, because there weren't > any real requests. > But now I am getting one. > Will the new ELN build implementation be able to do ELN Extra? > It would need to pull from the ELN Extra view on Content Resolvers, and build > against the eln-extra build target. > To me, that seems simple, but I'm not the one setting up the new build > implementation. > Yes, it will be able to do this. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: F35 Change: libffi 3.4 (late System-Wide Change proposal)
On Thu, Jul 15, 2021 at 12:31 PM Carlos O'Donell wrote: > On 7/15/21 6:52 AM, Zbigniew Jędrzejewski-Szmek wrote: > > On Wed, Jul 14, 2021 at 02:28:50PM -0400, Ben Cotton wrote: > >> == Release Notes == > >> > >> libffi does not public formal release notes. A change list can be > >> found in libffi's git history: > >> https://github.com/libffi/libffi/commits/master > > > > Those sentences are slightly garbled too. > > Upstream is providing release notes. I think he is referring to the use of "public" where "publish" is the correct word. -- 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: F35 Change: libffi 3.4 (late System-Wide Change proposal)
On Thu, Jul 15, 2021 at 02:28:20PM -0400, Carlos O'Donell wrote: > On 7/15/21 6:52 AM, Zbigniew Jędrzejewski-Szmek wrote: > > On Wed, Jul 14, 2021 at 02:28:50PM -0400, Ben Cotton wrote: > >> https://fedoraproject.org/wiki/Changes/LIBFFI34 > >> > >> == Summary == > >> Rebase libffi in Fedora 34 from libffi 3.1 to libffi 3.4 (released > >> June 28 2021), and provide a libffi3.1 compatibility package to handle > >> the library SONAME transition. > > > > The usual: please don't say "rebase" in public-facing documents. > > It's packaging jargon that is not clear to users. > > Switched to "Update" since that's what we're doing. > > Thanks for the feedback! I've been filing system-wide change requests for > years with glibc, and I was never quite sure of the exact audience that > might be reading them. I think nobody knows the exact audience, except that it's certainly very varied. For example, phoronix is a popular website and it often releases article directly based on the change text. This is pretty clear in the list of articles about F34 [1]. We also know that sometimes the change page lives on, like the merged-usr page [2], which is still being cited regularly. So I think getting the texts on those pages approachable and clear is very important. [1] https://www.phoronix.com/scan.php?page=search=Fedora+34 [2] https://fedoraproject.org/wiki/Features/UsrMove Zbyszek ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: [Fedocal] Reminder meeting : ELN SIG
This might not warrant a meeting, but it's something that just came up. ELN-Extra I never went beyond the Content Resolver initial setup, because there weren't any real requests. But now I am getting one. Will the new ELN build implementation be able to do ELN Extra? It would need to pull from the ELN Extra view on Content Resolvers, and build against the eln-extra build target. To me, that seems simple, but I'm not the one setting up the new build implementation. Troy On Fri, Jul 16, 2021 at 5:43 AM Stephen Gallagher wrote: > I don't currently have anything on the agenda for today's meeting. If > you have something, please reply to this email or I will just go ahead > and cancel for this week. > > On Thu, Jul 15, 2021 at 8:00 AM wrote: > > > > Dear all, > > > > You are kindly invited to the meeting: > >ELN SIG on 2021-07-16 from 12:00:00 to 13:00:00 US/Eastern > >At fedora-meet...@irc.libera.chat > > > > The meeting will be about: > > > > > > > > Source: https://calendar.fedoraproject.org//meeting/9920/ > > > > ___ > > devel mailing list -- devel@lists.fedoraproject.org > > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: buildSRPMFromSCM stuck
On Tue, 2021-07-13 at 19:21 +0200, david...@fedoraproject.org wrote: > On 7/13/21 5:48 PM, Kevin Fenzi wrote: > > On Tue, Jul 13, 2021 at 08:10:05AM +0200, David wrote: > > > Hi, > > > > > > I have been trying to build git-cola for EPEL8, but the > > > buildSRPMFromSCM > > > is stuck for over 5 hours: > > > https://koji.fedoraproject.org/koji/taskinfo?taskID=71779476 > > > > > > It is already the second try, the first I have canceled after 20 > > > hours. > > > > > > Is the autochangelog feature the cause? > > > > > > Is there something else I did wrong? > > > > Well, I can easily duplicate this here locally with a 'fedpkg srpm' > > in > > the epel8 branch. > > > > It looks like git is looping: > > > > ... > > 163004 newfstatat(AT_FDCWD, "/home/kevin/git/pkgs/git- > > cola/epel8/.git/objects/f4/", 0x7fffb9ce9d70, 0) = -1 ENOENT (No > > such file or directory) > > 163004 newfstatat(AT_FDCWD, "/home/kevin/git/pkgs/git- > > cola/epel8/.git/objects/71/", 0x7fffb9ce9d70, 0) = -1 ENOENT (No > > such file or directory) > > 163004 newfstatat(AT_FDCWD, "/home/kevin/git/pkgs/git- > > cola/epel8/.git/objects/f4/", 0x7fffb9ce9d70, 0) = -1 ENOENT (No > > such file or directory) > > 163004 newfstatat(AT_FDCWD, "/home/kevin/git/pkgs/git- > > cola/epel8/.git/objects/71/", 0x7fffb9ce9d70, 0) = -1 ENOENT (No > > such file or directory) > > ... > > > > So, I guess this is a rpmautospec bug? It appears to be one... > > Can you file it on the rpmautospec project? > > > > kevin > > Thanks a lot for analysing. > > I have filed https://pagure.io/fedora-infra/rpmautospec/issue/202 Thanks to both of you. I'll look into it -- this should work for EPEL8 packages, too. Nils -- Nils Philippsen / Software Engineer / Red Hat PGP fingerprint: D0C1 1576 CDA6 5B6E BBAE 95B2 7D53 7FCA E9F6 395D ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: rpmautospec deployment into production
On Sat, 2021-07-10 at 11:01 +, Mattia Verga via devel wrote: > Il 10/07/21 11:07, Robert-André Mauchin ha scritto: > > I haven't followed the dev of this project closely, is there a > > guide for packagers to explain how it works and how to integrate it > > to our workflow? > > > > Best regards, > > > > Robert-André > > I think it's https://pagure.io/docs/fedora-infra/rpmautospec/ Yes, thanks for linking to it! If there's anything missing or unclear, please file an issue here: https://pagure.io/fedora-infra/rpmautospec Nils -- Nils Philippsen / Software Engineer / Red Hat PGP fingerprint: D0C1 1576 CDA6 5B6E BBAE 95B2 7D53 7FCA E9F6 395D ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1983085] New: perl-Eval-LineNumbers-0.35 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1983085 Bug ID: 1983085 Summary: perl-Eval-LineNumbers-0.35 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Eval-LineNumbers Keywords: FutureFeature, Triaged Assignee: emman...@seyman.fr Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: emman...@seyman.fr, perl-devel@lists.fedoraproject.org Target Milestone: --- Classification: Fedora Latest upstream release: 0.35 Current version/release in rawhide: 0.34-21.fc35 URL: http://search.cpan.org/dist/Eval-LineNumbers/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/12473/ -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: rpmautospec deployment into production
Hi Michel, On Tue, 2021-07-13 at 17:27 -0700, Michel Alexandre Salim via devel wrote: > Now that this is in the Koji builders... would this be sufficient to > have it enabled for EPEL8 specs as well? > > - branch and build python-rpmautospec for EPEL8 > - add Requires: rpmautospec-rpm-macros to epel-rpm-macros in EPEL8 > > Given that EPEL8 will be around for a while, it sounds like it would be > of benefits if we can keep the same spec between Rawhide and it. e.g. > python-TestSlide now uses rpmautospec in the Rawhide branch, and so any > update in EPEL8 will have to diverge. in order to use rpmautospec features, it needs to be available on the builder machines (which are F34) and, for local operations, on the machine running fedpkg or equivalent. I.e. making it available on EL8 will help people whose work environment is RHEL8 or CentOS 8, it shouldn't be required to be able to build an EL8 package in our infrastructure. There seems to be a bug[1] which prevents building EL8 packages that use %autorelease, %autochangelog, which I'm investigating right now. I'd be happy to be able to offer rpmautospec client-side on EL8, too, but as you found out in [2], this needs a newer pygit2 version than what is available there. Nils [1]: https://pagure.io/fedora-infra/rpmautospec/issue/202 [2]: https://pagure.io/fedora-infra/rpmautospec/issue/204 -- Nils Philippsen / Software Engineer / Red Hat PGP fingerprint: D0C1 1576 CDA6 5B6E BBAE 95B2 7D53 7FCA E9F6 395D ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: [Fedocal] Reminder meeting : ELN SIG
I don't currently have anything on the agenda for today's meeting. If you have something, please reply to this email or I will just go ahead and cancel for this week. On Thu, Jul 15, 2021 at 8:00 AM wrote: > > Dear all, > > You are kindly invited to the meeting: >ELN SIG on 2021-07-16 from 12:00:00 to 13:00:00 US/Eastern >At fedora-meet...@irc.libera.chat > > The meeting will be about: > > > > Source: https://calendar.fedoraproject.org//meeting/9920/ > > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Unannounced soname bump: samba-client-libs (breaking sssd and so on)
Hello, all: samba is upgraded from samba-4.14.6-1.fc34 to samba-4.15.0-0.0.rc1.fc35, Its subpackage (samba-client-libs) contains libndr.so, which did soname bump: libndr.so.1()(64bit) -> libndr.so.2()(64bit) Currently this breaks rawhide tree: affected packages are: binary rpm sourcerpm evolution-mapi-0:3.41.1-1.fc35.x86_64 evolution-mapi-3.41.1-1.fc35.src.rpm freeipa-server-0:4.9.6-2.fc35.x86_64freeipa-4.9.6-2.fc35.src.rpm freeipa-server-trust-ad-0:4.9.6-2.fc35.x86_64 freeipa-4.9.6-2.fc35.src.rpm openchange-0:2.3-37.fc35.x86_64 openchange-2.3-37.fc35.src.rpm openchange-client-0:2.3-37.fc35.x86_64 openchange-2.3-37.fc35.src.rpm sssd-ad-0:2.5.2-1.fc35.x86_64 sssd-2.5.2-1.fc35.src.rpm sssd-common-pac-0:2.5.2-1.fc35.x86_64 sssd-2.5.2-1.fc35.src.rpm sssd-ipa-0:2.5.2-1.fc35.x86_64 sssd-2.5.2-1.fc35.src.rpm Especially, sssd breakage seems to be affecting lots of Livespin compose failure, including Fedora-Workstation-Live-Rawhide-20210716.n.0. Regards, Mamoru ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora-Cloud-34-20210716.0 compose check report
No missing expected images. Soft failed openQA tests: 1/8 (x86_64), 1/8 (aarch64) (Tests completed, but using a workaround for a known bug) Old soft failures (same test soft failed in Fedora-Cloud-34-20210715.0): ID: 929380 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/929380 ID: 929389 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi URL: https://openqa.fedoraproject.org/tests/929389 Passed openQA tests: 7/8 (x86_64), 7/8 (aarch64) -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1964651] F35FailsToInstall: perl-Padre
https://bugzilla.redhat.com/show_bug.cgi?id=1964651 Petr Pisar changed: What|Removed |Added Fixed In Version||fedora-obsolete-packages-35 ||-12 -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1964647] F35FailsToInstall: perl-Debug-Client
https://bugzilla.redhat.com/show_bug.cgi?id=1964647 Petr Pisar changed: What|Removed |Added Fixed In Version||fedora-obsolete-packages-35 ||-12 -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1964651] F35FailsToInstall: perl-Padre
https://bugzilla.redhat.com/show_bug.cgi?id=1964651 Bug 1964651 depends on bug 1964647, which changed state. Bug 1964647 Summary: F35FailsToInstall: perl-Debug-Client https://bugzilla.redhat.com/show_bug.cgi?id=1964647 What|Removed |Added Status|NEW |CLOSED Resolution|--- |CANTFIX -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1964647] F35FailsToInstall: perl-Debug-Client
https://bugzilla.redhat.com/show_bug.cgi?id=1964647 Petr Pisar changed: What|Removed |Added Status|NEW |CLOSED CC||ppi...@redhat.com Resolution|--- |CANTFIX Last Closed||2021-07-16 08:30:40 --- Comment #5 from Petr Pisar --- This bug is known to an upstream since 2020-09-26 without any response. We don't know how to fix it properly. This package is only used for perl-Padre which itself is upstream-dead for many years. Removed from Fedora 35. -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Review swaps: A bunch of PHP libraries
Hi all, I finally found some time to unbundle all the 3rdparty PHP/composer libraries from the nextcloud package. The bad news is that due to their various dependency trees, I now have a total of 24 new packages that need reviewing. The good news is that I think quite a few of them will be generally useful beyond just nextcloud. They are all fairly small & simple PHP libraries, build without issues and are basically identical in terms of packaging. If there are people out there who'd like to try their hand at reviewing for the first time, one of these might be a good place to start. Obviously, if you need something reviewed in return, I'd be happy to do that. Full list of links is below, but to make it easier for people - I set up a dependency tree ( https://bugzilla.redhat.com/buglist.cgi?bug_id=1981857_id_type=anddependson=tvp_id=12016550 ) so you can pick a leaf. - I made a copr repository ( https://copr.fedorainfracloud.org/coprs/lcts/nextcloud/packages/ ) that has builds for all of these, including fedora-review/rpmlint logs (and a big thank you to whoever made that last bit possible in Copr, that was *extremely* useful). The repo also contains a few forks of existing packages, ignore those :) . Best, Christopher List of links: https://bugzilla.redhat.com/show_bug.cgi?id=1982616 https://bugzilla.redhat.com/show_bug.cgi?id=1982618 https://bugzilla.redhat.com/show_bug.cgi?id=1982619 https://bugzilla.redhat.com/show_bug.cgi?id=1982621 https://bugzilla.redhat.com/show_bug.cgi?id=1982624 https://bugzilla.redhat.com/show_bug.cgi?id=1982627 https://bugzilla.redhat.com/show_bug.cgi?id=1982629 https://bugzilla.redhat.com/show_bug.cgi?id=1982630 https://bugzilla.redhat.com/show_bug.cgi?id=1982631 https://bugzilla.redhat.com/show_bug.cgi?id=1982632 https://bugzilla.redhat.com/show_bug.cgi?id=1982633 https://bugzilla.redhat.com/show_bug.cgi?id=1982635 https://bugzilla.redhat.com/show_bug.cgi?id=1982636 https://bugzilla.redhat.com/show_bug.cgi?id=1982637 https://bugzilla.redhat.com/show_bug.cgi?id=1982638 https://bugzilla.redhat.com/show_bug.cgi?id=1982639 https://bugzilla.redhat.com/show_bug.cgi?id=1982640 https://bugzilla.redhat.com/show_bug.cgi?id=1982643 https://bugzilla.redhat.com/show_bug.cgi?id=1982645 https://bugzilla.redhat.com/show_bug.cgi?id=1982646 https://bugzilla.redhat.com/show_bug.cgi?id=1982647 https://bugzilla.redhat.com/show_bug.cgi?id=1982648 https://bugzilla.redhat.com/show_bug.cgi?id=1982651 https://bugzilla.redhat.com/show_bug.cgi?id=1982652 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 815713] perl-Padre-1.00 is available
https://bugzilla.redhat.com/show_bug.cgi?id=815713 Petr Pisar changed: What|Removed |Added Status|NEW |CLOSED Resolution|--- |WONTFIX Last Closed||2021-07-16 08:26:48 --- Comment #8 from Petr Pisar --- This package was removed from Fedora 35 (bug #1964651). -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1964651] F35FailsToInstall: perl-Padre
https://bugzilla.redhat.com/show_bug.cgi?id=1964651 Petr Pisar changed: What|Removed |Added Status|NEW |CLOSED Resolution|--- |CANTFIX Last Closed||2021-07-16 08:25:07 --- Comment #5 from Petr Pisar --- Last upstream release in 2013. We cannot upgrade because of bundled WxScintilla. Requires unfixable perl-Debug-Client. This package was removed from Fedora 35. -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1982986] New: perl-TheSchwartz-1.16 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1982986 Bug ID: 1982986 Summary: perl-TheSchwartz-1.16 is available Product: Fedora Version: rawhide Status: NEW Component: perl-TheSchwartz Keywords: FutureFeature, Triaged Assignee: emman...@seyman.fr Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: emman...@seyman.fr, perl-devel@lists.fedoraproject.org Target Milestone: --- Classification: Fedora Latest upstream release: 1.16 Current version/release in rawhide: 1.15-5.fc35 URL: http://search.cpan.org/dist/TheSchwartz/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/14387/ -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1982979] New: perl-Data-Properties-1.05 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1982979 Bug ID: 1982979 Summary: perl-Data-Properties-1.05 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Data-Properties Keywords: FutureFeature, Triaged Assignee: emman...@seyman.fr Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: emman...@seyman.fr, perl-devel@lists.fedoraproject.org Target Milestone: --- Classification: Fedora Latest upstream release: 1.05 Current version/release in rawhide: 0.02-30.fc35 URL: https://metacpan.org/release/Data-Properties Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/17963/ -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora-Cloud-33-20210716.0 compose check report
No missing expected images. Soft failed openQA tests: 1/8 (x86_64), 1/8 (aarch64) (Tests completed, but using a workaround for a known bug) Old soft failures (same test soft failed in Fedora-Cloud-33-20210715.0): ID: 929364 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/929364 ID: 929373 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi URL: https://openqa.fedoraproject.org/tests/929373 Passed openQA tests: 7/8 (x86_64), 7/8 (aarch64) -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
