[EPEL-devel] Fedora EPEL 8 updates-testing report
The following Fedora EPEL 8 Security updates need testing: Age URL 0 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-4ca0c60e5b mbedtls-2.16.3-1.el8 The following builds have been pushed to Fedora EPEL 8 updates-testing perl-Test-Spelling-0.25-1.el8 Details about builds: perl-Test-Spelling-0.25-1.el8 (FEDORA-EPEL-2019-5525eeff39) Check for spelling errors in POD files Update Information: This is the first EPEL-8 build of perl-Test-Spelling. ___ 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
[389-devel] 389 DS nightly 2019-09-30 - 96% PASS
https://fedorapeople.org/groups/389ds/ci/nightly/2019/09/30/report-389-ds-base-1.4.2.2-20190929git2e85b4a.fc30.x86_64.html ___ 389-devel mailing list -- 389-devel@lists.fedoraproject.org To unsubscribe send an email to 389-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/389-devel@lists.fedoraproject.org
[EPEL-devel] Fedora EPEL 7 updates-testing report
The following Fedora EPEL 7 Security updates need testing: Age URL 411 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-3c9292b62d condor-8.6.11-1.el7 187 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-d2c1368294 cinnamon-3.6.7-5.el7 153 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-c499781e80 python-gnupg-0.4.4-1.el7 150 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-bc0182548b bubblewrap-0.3.3-2.el7 87 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-12067fc897 dosbox-0.74.3-2.el7 13 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-330b323bb6 golang-1.13-1.el7 10 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-209b03a8a4 cryptopp-5.6.5-1.el7 6 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-7410520bec blis-0.6.0-4.el7 5 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-81572ab529 chromium-77.0.3865.90-2.el7 4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-1c8bc2bf57 mosquitto-1.6.7-1.el7 2 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-600b4ad49c yara-3.10.0-3.el7 0 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-8b6b5df244 mbedtls-2.7.12-1.el7 The following builds have been pushed to Fedora EPEL 7 updates-testing mozilla-ublock-origin-1.22.4-1.el7 qt5-qtstyleplugins-5.0.0-29.el7 spirv-tools-2019.1-4.el7 Details about builds: mozilla-ublock-origin-1.22.4-1.el7 (FEDORA-EPEL-2019-df8034d1ea) An efficient blocker for Firefox Update Information: This is an emergency fix. The issue was [fixed in dev build days ago](https://g ithub.com/gorhill/uBlock/commit/97d6d5028b948a6d4e0cbf40cdb21486f64d39b1), and it was originally deemed to not be a serious regression. However as [reported by a user on Reddit](https://www.reddit.com/r/uBlockOrigin/comments/d8jyy9/nthan cestor_blocking_completely_broken_on/), the issue was affecting more than just the logging of cosmetic filters, it was completely breaking cosmetic filtering when the two following conditions were met: * uBO's own logger was opened; AND * Procedural cosmetic filters were injected on the page. ChangeLog: * Sat Sep 28 2019 Dominik Mierzejewski - 1.22.4-1 - update to 1.22.4 (#1756060) References: [ 1 ] Bug #1756060 - mozilla-ublock-origin-1.22.4 is available https://bugzilla.redhat.com/show_bug.cgi?id=1756060 qt5-qtstyleplugins-5.0.0-29.el7 (FEDORA-EPEL-2019-14616904a4) Classic Qt widget styles Update Information: Rebuild for RHEL 7.7 ChangeLog: * Fri Sep 21 2018 Jan Grulich - 5.0.0-29 - rebuild (qt5) * Sat Jul 14 2018 Fedora Release Engineering - 5.0.0-28 - Rebuilt for https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild References: [ 1 ] Bug #1756340 - Qt styleplugins dependencies broken by upgrade to version 7.7 https://bugzilla.redhat.com/show_bug.cgi?id=1756340 spirv-tools-2019.1-4.el7 (FEDORA-EPEL-2019-2c04a2ffb5) API and commands for processing SPIR-V modules Update Information: Update to avoid problems with vulkan in RHEL7.7 ChangeLog: * Sun Sep 29 2019 Dave Airlie 2019.1-4 - Update to avoid problems with vulkan in RHEL7.7 * Sun Sep 29 2019 Dave Airlie - 2019.1-3 - Update to avoid problems with vulkan in RHEL7.7 * Sun Sep 29 2019 Dave Airlie - 2019.1-2 - Update to avoid problems with vulkan in RHEL7.7 References: [ 1 ] Bug #1745104 - spirv-tools conflicts with vulkan from 7.7 https://bugzilla.redhat.com/show_bug.cgi?id=1745104 [ 2 ] Bug #1753100 - spirv-tools-libs conflict with vulkan package https://bugzilla.redhat.com/show_bug.cgi?id=1753100 ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to
suitesparse 5.4 coming to rawhide soon
This includes a soname bump to libsuitesparseconfig.so which near as I can tell is only used by octave, so I'll be rebuilding that as well. COPR is here if you want to test it out: https://copr.fedorainfracloud.org/coprs/orion/suitesparse/ Need to see if the ppc64le failure is a new thing or not as well. -- Orion Poplawski Manager of NWRA Technical Systems 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 https://www.nwra.com/ smime.p7s Description: S/MIME Cryptographic 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
Backend storage clean-up
Hello, we have decided that it is a time to go through Copr backend data and clean it up a little. Due to several bugs forgetting to remove backend data after removing their records from the database, _temporarily_ backing up some folder here and there, etc, we ended up with a lot of unknown data, that should have been already deleted. So, we wrote a script [1] to find data that should be deleted, and we ... haven't deleted it yet. Instead, we put it aside in a case there were any false-positives by the script. If you want to be extra safe, I am attaching a list of all of those files, you may check it. If you find out, that we accidentally want to remove any of your data that is still being used, please contact us immediately! Otherwise, we are going to delete it once we are running out of disk space (which may not take a lot of time) [1] https://pagure.io/copr/copr/blob/master/f/backend/run/copr_print_results_to_delete.py Thank you for understanding, Jakub results-to-delete.xz Description: application/xz ___ 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
Re: HEADS-UP: Asciidoctor 2.0.10
Hi, I wrote: > I'm planning to push asciidoctor-2.0.10 to rawhide in the > next few days. This has now been built and should show up in the next rawhide compose. > This is a major bump from our current 1.5.8, but upstream > has worked hard to fix regressions found since the initial > 2.0.0 release back in March. > > The 2.0.0 release notes can be found at: > > https://github.com/asciidoctor/asciidoctor/releases/tag/v2.0.0 > > The subsequent minor release are covered at: > > https://github.com/asciidoctor/asciidoctor/releases -- Todd ___ 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
Re: HEADS-UP: Asciidoctor 2.0.10
Hi Fabio, Fabio Valentini wrote: > I'm the maintainer of rubygem-jekyll-asciidoc, and I think there > shouldn't be issues with it when updating rubygem-asciidoctor. > The Jekyll AsciiDoc plugin is published by the asciidoctor project > themselves, so I just hope they know what they're doing :) Heh, I hope so also. We'll find out soon, as I've just built asciidoctor-2.0.10 in rawhide. -- Todd ___ 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
Re: koji builds failing with "GenericError: Build already in progress (task …)"
On Sun, 29 Sep 2019 at 14:11, Zbigniew Jędrzejewski-Szmek wrote: > I have seen this a few times lately. When a build is started for > rawhide, and in succession builds for other branches, they fail. > > Example: > https://koji.fedoraproject.org/koji/taskinfo?taskID=37938969 (build > target: rawhide) > https://koji.fedoraproject.org/koji/taskinfo?taskID=37938975 (build > target: f31-candidate, > fails with GenericError: Build already in progress (task 37938969)) > > Trying the rebuild again succeeds. > > Known issue? > Yesterday I've hit the same issue trying to repeat the build mc without bumping release after small cleanup in git. All what you need to do is execute "fedpkg build --scratch". kloczek -- Tomasz Kłoczko | LinkedIn: http://lnkd.in/FXPWxH ___ 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
[EPEL-devel] Re: libssh2 issues in EPEL8 buildroot
On 8/14/19 6:40 PM, Stephen John Smoogen wrote: On Wed, 14 Aug 2019 at 18:07, Orion Poplawski wrote: I see virt modules (from dnf module info virt): 820190510171727 - libssh2-0:1.8.0-7.module+el8.0.0+3075+09be6b65.1 820190516125745 - libssh2-0:1.8.0-7.module+el8.0.0+3075+09be6b65.1 820190529063309 - libssh2-0:1.8.0-7.module+el8.0.0+3075+09be6b65.1 820190618154454 - libssh2-0:1.8.0-7.module+el8.0.0.z+3418+a72cf898.1 820190226174025 - libssh2-0:1.8.0-7.module+el8+2833+c7d6d092 and virt-devel: 820190226174025: - libssh2-devel-0:1.8.0-7.module+el8+2833+c7d6d092 Seems to me like the EPEL8 builder is failing to pick up 820190226174025 virt module - possibly because the version does not sort higher than 820190618154454 ? Which seems perfectly understandable to me, but I have no idea how this is all supposed to work. Okay, I see your point now - we're missing the 820190618154454 virt-devel module... FWIW - I've filed https://bugzilla.redhat.com/show_bug.cgi?id=1741362 Yeah the problem is that the 2 sets of modules have to match up for this work. We could try to keep the old one for building but I believe it has cve's in it. I think in the end I may just remove the virt-devel from the build system until they get it fixed as it is not helping in anyway. This appears to be resolved now with the release of 820190828150510 -- Orion Poplawski Manager of NWRA Technical Systems 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 https://www.nwra.com/ smime.p7s Description: S/MIME Cryptographic 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
Re: koji builds failing with "GenericError: Build already in progress (task …)"
On Sun, Sep 29, 2019 at 10:50:37PM +0900, Mamoru TASAKA wrote:
> Zbigniew Jędrzejewski-Szmek wrote on 2019/09/29 22:02:
> >I have seen this a few times lately. When a build is started for
> >rawhide, and in succession builds for other branches, they fail.
> >
> >Example:
> >https://koji.fedoraproject.org/koji/taskinfo?taskID=37938969 (build target:
> >rawhide)
> >https://koji.fedoraproject.org/koji/taskinfo?taskID=37938975 (build target:
> >f31-candidate,
> > fails with GenericError: Build already in progress (task 37938969))
> >
> >Trying the rebuild again succeeds.
> >
> >Known issue?
>
> Because you are actually building the same EVR (python-deap-1.3.0-1) on both
> rawhide and f31-candidate. Note that there is no %{?dist} in release.
Oops, my bad! Thanks!
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
[Bug 1756737] perl-Mojolicious-8.25 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1756737 Emmanuel Seyman changed: What|Removed |Added Status|NEW |CLOSED Fixed In Version||perl-Mojolicious-8.25-1.fc3 ||2 Resolution|--- |RAWHIDE Last Closed||2019-09-29 14:16:04 --- Comment #1 from Emmanuel Seyman --- Built for rawhide: https://koji.fedoraproject.org/koji/buildinfo?buildID=1392373 -- 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
Re: koji builds failing with "GenericError: Build already in progress (task …)"
Zbigniew Jędrzejewski-Szmek wrote on 2019/09/29 22:02:
I have seen this a few times lately. When a build is started for
rawhide, and in succession builds for other branches, they fail.
Example:
https://koji.fedoraproject.org/koji/taskinfo?taskID=37938969 (build target:
rawhide)
https://koji.fedoraproject.org/koji/taskinfo?taskID=37938975 (build target:
f31-candidate,
fails with GenericError: Build already in progress (task 37938969))
Trying the rebuild again succeeds.
Known issue?
Because you are actually building the same EVR (python-deap-1.3.0-1) on both
rawhide and f31-candidate. Note that there is no %{?dist} in release.
Zbyszek
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
[Bug 1756737] New: perl-Mojolicious-8.25 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1756737 Bug ID: 1756737 Summary: perl-Mojolicious-8.25 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Mojolicious 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, robinlee.s...@gmail.com, yan...@declera.com Target Milestone: --- Classification: Fedora Latest upstream release: 8.25 Current version/release in rawhide: 8.24-1.fc32 URL: https://metacpan.org/release/Mojolicious Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/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/5966/ -- 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
koji builds failing with "GenericError: Build already in progress (task …)"
I have seen this a few times lately. When a build is started for rawhide, and in succession builds for other branches, they fail. Example: https://koji.fedoraproject.org/koji/taskinfo?taskID=37938969 (build target: rawhide) https://koji.fedoraproject.org/koji/taskinfo?taskID=37938975 (build target: f31-candidate, fails with GenericError: Build already in progress (task 37938969)) Trying the rebuild again succeeds. Known issue? 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
Orphaned pegdown (leaf package)
Hi everybody, I have just orphaned the "pegdown" package, which has become a leaf package in rawhide. Its only dependent packages in fedora were maven-doxia and maven-doxia-sitetools, but the latest builds in rawhide have disabled the markdown support in these packages, and their latest upstream releases have transitioned away from pegdown to a different markdown implementation anyway (which isn't packaged for fedora). Fabio ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 31 Beta Release Announcement
On Sun, Sep 29, 2019 at 3:48 AM Kevin Kofler wrote: > > Fabio Valentini wrote: > > To make things even more interesting, the non-modular Java stack has > > almost reached parity with what's available from the shiny module > > branches, except a handful of packages that require more work than a > > simple "bump version and build" (for example, the rebase from maven > > 3.5 to 3.6 is still pending, but I'm planning to work on that soon). > > Does that include Eclipse, where the packagers recently announced that it > would become module-only? > > (That said, all the Java projects I work with are set up for NetBeans, so I > don't really use Eclipse anyway. I'm just asking for curiosity. Sadly, the > NetBeans Fedora package was abandoned long ago, long before Modularity has > become a thing, so that one is a wholly different story.) No, it doesn't include eclipse. We aren't interested in maintaining it, and certainly don't have the manpower to do it. Fabio > Kevin Kofler > ___ > 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 ___ 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
[Bug 1756564] perl-PDF-Create-1.45 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1756564 --- Comment #5 from Upstream Release Monitoring --- the-new-hotness/release-monitoring@fedoraproject.org's scratch build of perl-PDF-Create-1.45-1.fc29.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=37934968 -- 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
[Bug 1756564] perl-PDF-Create-1.45 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1756564 --- Comment #4 from Upstream Release Monitoring --- Created attachment 1620745 --> https://bugzilla.redhat.com/attachment.cgi?id=1620745=edit [patch] Update to 1.45 (#1756564) -- 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
[Bug 1756564] perl-PDF-Create-1.45 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1756564 Upstream Release Monitoring changed: What|Removed |Added Summary|perl-PDF-Create-1.44 is |perl-PDF-Create-1.45 is |available |available --- Comment #3 from Upstream Release Monitoring --- Latest upstream release: 1.45 Current version/release in rawhide: 1.43-7.fc31 URL: http://search.cpan.org/dist/PDF-Create/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/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/5987/ -- 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
[Bug 1756609] perl-GDGraph packages for EPEL 8
https://bugzilla.redhat.com/show_bug.cgi?id=1756609 Paul Howarth changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|tcall...@redhat.com |p...@city-fan.org --- Comment #1 from Paul Howarth --- https://pagure.io/releng/fedora-scm-requests/issue/17439 https://pagure.io/releng/fedora-scm-requests/issue/17440 -- 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
[Bug 1755576] perl-DBIx-Class-DeploymentHandler-0.002233 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1755576 Emmanuel Seyman changed: What|Removed |Added Status|NEW |CLOSED Fixed In Version||perl-DBIx-Class-DeploymentH ||andler-0.002233-1.fc32 Resolution|--- |RAWHIDE Last Closed||2019-09-29 07:58:09 --- Comment #1 from Emmanuel Seyman --- Built for rawhide: https://koji.fedoraproject.org/koji/buildinfo?buildID=1392322 -- 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
Re: gnome-subtitles (mono) dependency on libenchant.so.1 not picked up automatically
Julian Sikorski wrote on 2019/09/29 16:02:
Hi list,
a bug was recently filed against gnome-subtitles [1] stating that
libenchant.so.1 dependency is missing. While I could easily fix this
with explicit Requires, my concern is why wasnt't this depencency picked
up automatically in the first place. Do you have any suggestions? Thank you!
Best regards,
Julian
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1750161
The rebuilt binary is not linked against libenchant.so. Actually enchant{-devel}
does not appear in buildroot (as gnome-subtitles README file says enchant is
not needed for build time dependency). gnome-subtitles binary dlopen()s
libenchant.so on runtime, and rpmbuild cannot detect such runtime behavior.
The explicit "Requires:" is needed for this case. (Or you can modify
gnome-subtitiles
not to dlopen() libenchant.so.1 but to link against libenchant.so.1 beforehand,
but
it may be non-easy work.)
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
gnome-subtitles (mono) dependency on libenchant.so.1 not picked up automatically
Hi list, a bug was recently filed against gnome-subtitles [1] stating that libenchant.so.1 dependency is missing. While I could easily fix this with explicit Requires, my concern is why wasnt't this depencency picked up automatically in the first place. Do you have any suggestions? Thank you! Best regards, Julian [1] https://bugzilla.redhat.com/show_bug.cgi?id=1750161 ___ 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
