[Bug 1796214] perl-CDB_File-1.02 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1796214 Bug 1796214 depends on bug 1826270, which changed state. Bug 1826270 Summary: Review Request: perl-B-COW - Additional B helpers to check Copy On Write status https://bugzilla.redhat.com/show_bug.cgi?id=1826270 What|Removed |Added Status|ON_QA |CLOSED Resolution|--- |ERRATA -- 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
[EPEL-devel] Re: Looking for someone to take ngircd in EPEL
On 5/1/20 8:39 AM, Kevin Fenzi wrote: On Thu, Apr 30, 2020 at 08:39:48PM -0600, Orion Poplawski wrote: Anyone willing to take over ngircd for EPEL? https://bugzilla.redhat.com/show_bug.cgi?id=1830182 Sure. I can do that. Will add it to my list. kevin ___ Thanks, kevin! -- 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
[Bug 1824317] perl-Text-ASCIITable: please add epel8 branch
https://bugzilla.redhat.com/show_bug.cgi?id=1824317 Fedora Update System changed: What|Removed |Added Status|ON_QA |CLOSED Fixed In Version||perl-Text-ASCIITable-0.22-1 ||1.el8 Resolution|--- |ERRATA Last Closed||2020-05-03 04:18:58 --- Comment #4 from Fedora Update System --- FEDORA-EPEL-2020-973942af97 has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. ___ 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
error in spec file
Hello, I have been trying to package franz from here: https://github.com/meetfranz/franz/archive/v5.5.0.tar.gz and I have the following spec file at: UNTITLED - Pastebin Service | | | | UNTITLED - Pastebin Service | | | However, I get a bunch of warnings and errors and I am not sure how to get around this. Because it is a long list, here it is as a file: UNTITLED - Pastebin Service | | | | UNTITLED - Pastebin Service | | | Any suggestions as to what I am doing wrong is very appreciated. TIA! ___ 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
[389-devel] 389 DS nightly 2020-05-03 - 88% PASS
https://fedorapeople.org/groups/389ds/ci/nightly/2020/05/03/report-389-ds-base-1.4.4.1-20200502git8895fc4.fc31.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
Re: Grub, EFI, and SELinux
On Sat, May 2, 2020 at 4:33 AM Christopher wrote: > Those are bugs filed against RPM. Is the RPM package responsible for > executing lsetfilecon, or is it the grub2 package? If the grub2 > package, it seems to me that they should know that EFI partitions will > never support lsetfilecon and they should never try. If it's RPM, then > it looks like it is suppressed upstream and the fix will be > incorporated eventually. I guess I don't know which component is > actually responsible for causing the execution of lsetfilecon. You're right, but there is discussion of the grub2 issue in bug 1722766. A number of bugs have been filed against grub2 specifically: https://bugzilla.redhat.com/show_bug.cgi?id=1819817 https://bugzilla.redhat.com/show_bug.cgi?id=1827922 https://bugzilla.redhat.com/show_bug.cgi?id=1829137 https://bugzilla.redhat.com/show_bug.cgi?id=1830399 So far, though, no word from the maintainer on those bugs. -- 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
Re: Fedora 33 System-Wide Change proposal: Node.js 14.x by default
On 01. 05. 20 22:21, Ben Cotton wrote: * Proposal owners: The packages are already built for Fedora 33 in a non-default module stream. On June 14th, 2020, the nodejs-14.x packages will become the default in Fedora 33 (either by making the 14.x module stream be the default stream or by rebuilding the packages as non-modular, depending on other factors). Will there be an attempted mass rebuild of the dependent packages? -- 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
[EPEL-devel] Re: Python macro backports for EPEL reviews needed
On 01. 05. 20 20:32, Troy Dawson wrote: I've never un-updated anything, and I'm not sure if it will make it possible for your packages to be pushed to stable. It wont. Just please make sure my commit eventually gets pushed in some update and that there is a buildroot override until that happens. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ 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: orphaning bleachbit
Silvia, read this https://fedoraproject.org/wiki/Join_the_package_collection_maintainers , also make some reviews to others packagers, after that, I or any sponsor can help you to join to the package maintainer group On Sat, May 2, 2020 at 11:46 AM Silvia Sánchez wrote: > > > For the records, I'm still interested in co-maintaining this package. > Please, let me know which are the next steps. > > > > > > On Sat, 2 May 2020 at 01:21, Alessio wrote: >> >> On Tue, 2019-12-31 at 10:09 +0300, Silvia Sánchez wrote: >> > >> > I'm perfectly fine with Fedora's policy regarding Python2. When >> > upstream updates to 3, I'll be happy to comaintain together with >> > Alessio. >> >> For the record, bleachbit 4 supporting python 3 was released a couple >> of weeks ago. >> >> >> Ciao, >> A. >> ___ >> 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 -- Eduardo Echeverria @echevemaster ___ 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 1830579] New: perl-YAML-LibYAML-0.82 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1830579 Bug ID: 1830579 Summary: perl-YAML-LibYAML-0.82 is available Product: Fedora Version: rawhide Status: NEW Component: perl-YAML-LibYAML Keywords: FutureFeature, Triaged Assignee: jples...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: jples...@redhat.com, mmasl...@redhat.com, p...@city-fan.org, perl-devel@lists.fedoraproject.org, trem...@tremble.org.uk Target Milestone: --- Classification: Fedora Latest upstream release: 0.82 Current version/release in rawhide: 0.81-1.fc32 URL: http://search.cpan.org/dist/YAML-LibYAML/ 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/3548/ -- 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
[EPEL-devel] Re: Playground policy
On 5/1/20 12:39 PM, Kevin Fenzi wrote: There was no 'rule' but the intent was everyone would keep the package.cfg and build for both. If they were not making any playground changes, they didn't need to commit anything, and fedpkg build would just build for both epel8 and epel8-playground. The problem is that the packages.cfg commit annoys everyone who does a 'merge origin/master' because it's not on the master branch, so they delete it to get their workflow back. I'd like to look at seeing if we can accomplish what we wanted with playground by having it just inherit from epel8. Failing that, we could just look at dropping playground if it's not useful for people. Yeah, having epel8-playground automatically inherit from epel8 would solve a lot of issues, it seems. I personally don't mind merging from master -- I don't want to build every Fedora revision for EPEL -- but I can understand how some maintainers might prefer otherwise. The purpose of epel8-playground is to diverge when needed. That's why the epel8 branch contains package.cfg by default. That seems to be the case for packages branched normally (fedpkg request-branch). *However* I've seen some packages where the epel8 branch and master branch are identical -- not sure how it happens, maybe the committer has force-push permission? Or is there a way to request that a branch be cloned from another branch instead of created from scratch? There's no force-push allowed. They likely just deleted it and are merging master over it. Interesting. Could you help take a look at - python-mimeparse - python-testscenarios and help figure out how epel8 and master end up sharing a history? Thanks, -- Michel Alexandre Salim profile: https://keybase.io/michel_slm chat via email: https://delta.chat/ GPG key: 96A7 A6ED FB4D 2113 4056 3257 CAF9 AD10 ACB1 BEF2 ___ 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: games group in comps
> Does anyone know why they are all optional there? Don't know why they are optional but most packages from this list will not run or retired already. I want to suggest add game launchers here which already packaged in Fedora: - minigalaxy - gamehub - legendary - lutris ___ 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
Fedora rawhide compose report: 20200502.n.0 changes
OLD: Fedora-Rawhide-20200430.n.1 NEW: Fedora-Rawhide-20200502.n.0 = SUMMARY = Added images:0 Dropped images: 0 Added packages: 3 Dropped packages:2 Upgraded packages: 80 Downgraded packages: 0 Size of added packages: 4.07 MiB Size of dropped packages:181.48 KiB Size of upgraded packages: 4.93 GiB Size of downgraded packages: 0 B Size change of upgraded packages: -255.80 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = = DROPPED IMAGES = = ADDED PACKAGES = Package: legendary-0.0.6-2.fc33 Summary: Free and open-source replacement for the Epic Games Launcher RPMs:legendary Size:98.67 KiB Package: nginx-1:1.18.0-1.module_f33+8817+fc310435 Summary: A high performance web server and reverse proxy server RPMs:nginx nginx-all-modules nginx-filesystem nginx-mod-http-image-filter nginx-mod-http-perl nginx-mod-http-xslt-filter nginx-mod-mail nginx-mod-stream Size:3.89 MiB Package: python-language-server-0.31.10-2.fc33 Summary: Python Language Server for the Language Server Protocol RPMs:python3-language-server Size:86.38 KiB = DROPPED PACKAGES = Package: guessencoding-1.4-19.fc32 Summary: Guess encoding of files and return configured reader RPMs:guessencoding guessencoding-javadoc Size:38.78 KiB Package: wingpanel-indicator-ayatana-2.0.3-10.fc32 Summary: Ayatana Indicator for wingpanel RPMs:wingpanel-indicator-ayatana Size:142.70 KiB = UPGRADED PACKAGES = Package: CubicSDR-0.2.5-4.20200226gitd2f9333.fc33 Old package: CubicSDR-0.2.5-3.20200226gitd2f9333.fc33 Summary: Cross-Platform Software-Defined Radio Panadapter RPMs: CubicSDR Size: 6.04 MiB Size change: -2.91 KiB Changelog: * Mon Apr 20 2020 Matt Domsch 0.2.5-4.20200407gitd2f9333 - rebuild for hamlib-devel 4.0.0 Package: autowrap-0.22.0-1.fc33 Old package: autowrap-0.19.1-2.fc32 Summary: Generates Python Extension modules from [Cython] PXD files RPMs: python3-autowrap Size: 93.37 KiB Size change: 1.35 KiB Changelog: * Fri May 01 2020 Antonio Trande - 0.22.0-1 - Release 0.22.0 Package: awscli-1.18.50-1.fc33 Old package: awscli-1.18.49-1.fc33 Summary: Universal Command Line Environment for AWS RPMs: awscli Size: 1.72 MiB Size change: -265 B Changelog: * Fri May 01 2020 Gwyn Ciesla - 1.18.50-1 - 1.18.50 Package: bashtop-0.8.18-1.fc33 Old package: bashtop-0.8.17-1.fc33 Summary: Linux resource monitor RPMs: bashtop Size: 51.82 KiB Size change: 1.19 KiB Changelog: * Fri May 01 2020 Germano Massullo - 0.8.17-2 - Disabled weak dependencies on EPEL7, since Recommends is not supported * Fri May 01 2020 Germano Massullo - 0.8.18-1 - 0.8.18 release Package: buildah-1.15.0-0.48.dev.gitf35e7d4.fc33 Old package: buildah-1.15.0-0.42.dev.git0b9a534.fc33 Summary: A command line tool used for creating OCI Images RPMs: buildah buildah-tests Size: 87.77 MiB Size change: 19.18 KiB Changelog: * Tue Apr 28 2020 RH Container Bot - 1.15.0-0.43.dev.gitbea8692 - autobuilt bea8692 * Tue Apr 28 2020 RH Container Bot - 1.15.0-0.44.dev.git8169acd - autobuilt 8169acd * Fri May 01 2020 RH Container Bot - 1.15.0-0.45.dev.git3af27b4 - autobuilt 3af27b4 * Fri May 01 2020 RH Container Bot - 1.15.0-0.46.dev.git63567cb - autobuilt 63567cb * Fri May 01 2020 RH Container Bot - 1.15.0-0.47.dev.git42a48f9 - autobuilt 42a48f9 * Fri May 01 2020 RH Container Bot - 1.15.0-0.48.dev.gitf35e7d4 - autobuilt f35e7d4 Package: cjdns-20.6-2.fc33 Old package: cjdns-20.6-1.fc33 Summary: The privacy-friendly network without borders RPMs: cjdns cjdns-graph cjdns-selinux cjdns-tools python3-cjdns Size: 3.02 MiB Size change: 574.95 KiB Changelog: * Wed Apr 29 2020 Stuart Gathman - 20.6-2 - Disable SECCOMP by default for armv7hl instead of excluding arch Package: console-login-helper-messages-0.18.1-1.fc33 Old package: console-login-helper-messages-0.18-1.fc33 Summary: Combines motd, issue, profile features to show system information to the user before/on login RPMs: console-login-helper-messages console-login-helper-messages-issuegen console-login-helper-messages-motdgen console-login-helper-messages-profile Size: 51.21 KiB Size change: 272 B Changelog: * Thu Apr 30 2020 Robert Fairley - 0.18.1-1 - Update to 0.18.1 Package: copyq-3.11.0-1.fc33 Old package: copyq-3.10.0-1.fc32 Summary: Advanced clipboard manager RPMs: copyq Size: 10.82 MiB Size change: 180.33 KiB Changelog: * Fri May 01 2020 Gerald Cox - 3.11.0-1 - Upstream release rhbz#1830240 Package: crawl-0.24.1-2.fc33 Old package: crawl-0.24.1-1.fc33 Summary: Roguelike dungeon exploration game RPMs: crawl crawl-common-data crawl-tiles crawl-tiles-data Size: 49.92 MiB Size
Re: Aarch64 build failure: hidden symbol `__aarch64_ldadd4_acq_rel' in /usr/lib/gcc/aarch64-redhat-linux/10/libgcc.a(ldadd_4_4.o) is referenced by DSO
On Sat, May 02, 2020 at 11:51:57AM -0500, Rex Dieter wrote: > Jakub Jelinek wrote: > > > On Sat, May 02, 2020 at 12:36:29PM +0200, Sandro Mani wrote: > >> Hi > >> > >> I'm stuck on the following build failure of the aarch64 build here [1] > >> > >> /usr/bin/ld: .libs/geod: hidden symbol `__aarch64_ldadd4_acq_rel' in > >> /usr/lib/gcc/aarch64-redhat-linux/10/libgcc.a(ldadd_4_4.o) is referenced > >> by DSO > >> /usr/bin/ld: final link failed: bad value > >> collect2: error: ld returned 1 exit status > >> > >> Never seen anything like this, any ideas? > > > > #1830472 > > wouldn't it have been better to untag the broken build asap so folks can > continue working? (Sorry if there was discussion about that possibility, > but I didn't see anything) > > As-is, everyone is blocking on waiting for the new gcc build to complete > (that koji estimates is another ~6 hours away). > > Personally, this morning was my primary chance to get a significant amount > of work done for the coming week... lost. :( I just untagged it. It should be out in the next newrepo. Sorry for not doing it sooner. kevin signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
games group in comps
Greetings. There's a ticket https://pagure.io/fedora-comps/issue/492 (formerly a bug) that the games group in comps has nothing in it. Thats not quite the case, it has a ton of games in it, but they are all optional. ;( I have no much horse in this race, but I thought I would see if folks here had ideas to improve this. Right now, 'dnf group install games' just doesn't do anything. Should it? Which games should it have? Does someone want to curate it? Does anyone know why they are all optional there? kevin signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Aarch64 build failure: hidden symbol `__aarch64_ldadd4_acq_rel' in /usr/lib/gcc/aarch64-redhat-linux/10/libgcc.a(ldadd_4_4.o) is referenced by DSO
Jakub Jelinek wrote: > On Sat, May 02, 2020 at 12:36:29PM +0200, Sandro Mani wrote: >> Hi >> >> I'm stuck on the following build failure of the aarch64 build here [1] >> >> /usr/bin/ld: .libs/geod: hidden symbol `__aarch64_ldadd4_acq_rel' in >> /usr/lib/gcc/aarch64-redhat-linux/10/libgcc.a(ldadd_4_4.o) is referenced >> by DSO >> /usr/bin/ld: final link failed: bad value >> collect2: error: ld returned 1 exit status >> >> Never seen anything like this, any ideas? > > #1830472 wouldn't it have been better to untag the broken build asap so folks can continue working? (Sorry if there was discussion about that possibility, but I didn't see anything) As-is, everyone is blocking on waiting for the new gcc build to complete (that koji estimates is another ~6 hours away). Personally, this morning was my primary chance to get a significant amount of work done for the coming week... lost. :( -- Rex ___ 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: orphaning bleachbit
For the records, I'm still interested in co-maintaining this package. Please, let me know which are the next steps. On Sat, 2 May 2020 at 01:21, Alessio wrote: > On Tue, 2019-12-31 at 10:09 +0300, Silvia Sánchez wrote: > > > > I'm perfectly fine with Fedora's policy regarding Python2. When > > upstream updates to 3, I'll be happy to comaintain together with > > Alessio. > > For the record, bleachbit 4 supporting python 3 was released a couple > of weeks ago. > > > Ciao, > A. > ___ > 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
[Test-Announce] Fedora 33 Rawhide 20200502.n.0 nightly compose nominated for testing
Announcing the creation of a new nightly release validation test event for Fedora 33 Rawhide 20200502.n.0. 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 - 20200425.n.0: anaconda-33.11-1.fc33.src, 20200502.n.0: anaconda-33.12-1.fc33.src lorax - 20200425.n.0: lorax-33.1-1.fc33.src, 20200502.n.0: lorax-33.2-1.fc33.src pungi - 20200425.n.0: pungi-4.2.1-2.fc33.src, 20200502.n.0: pungi-4.2.2-1.fc33.src Test coverage information for the current release can be seen at: https://www.happyassassin.net/testcase_stats/33 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_33_Rawhide_20200502.n.0_Summary The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora_33_Rawhide_20200502.n.0_Installation https://fedoraproject.org/wiki/Test_Results:Fedora_33_Rawhide_20200502.n.0_Base https://fedoraproject.org/wiki/Test_Results:Fedora_33_Rawhide_20200502.n.0_Server https://fedoraproject.org/wiki/Test_Results:Fedora_33_Rawhide_20200502.n.0_Cloud https://fedoraproject.org/wiki/Test_Results:Fedora_33_Rawhide_20200502.n.0_Desktop https://fedoraproject.org/wiki/Test_Results:Fedora_33_Rawhide_20200502.n.0_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 ___ 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: Aarch64 build failure: hidden symbol `__aarch64_ldadd4_acq_rel' in /usr/lib/gcc/aarch64-redhat-linux/10/libgcc.a(ldadd_4_4.o) is referenced by DSO
On Sat, 2 May 2020 12:36:29 +0200, Sandro Mani wrote: > Hi > > I'm stuck on the following build failure of the aarch64 build here [1] > > /usr/bin/ld: .libs/geod: hidden symbol `__aarch64_ldadd4_acq_rel' in > /usr/lib/gcc/aarch64-redhat-linux/10/libgcc.a(ldadd_4_4.o) is referenced > by DSO > /usr/bin/ld: final link failed: bad value > collect2: error: ld returned 1 exit status > > Never seen anything like this, any ideas? Since it's about libgcc and aarch64, it's very likely related to the earlier thread "Hundreds of aarch64 failures with gcc 10.0.1-0.13". ___ 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: Aarch64 build failure: hidden symbol `__aarch64_ldadd4_acq_rel' in /usr/lib/gcc/aarch64-redhat-linux/10/libgcc.a(ldadd_4_4.o) is referenced by DSO
On Sat, May 02, 2020 at 12:36:29PM +0200, Sandro Mani wrote: > Hi > > I'm stuck on the following build failure of the aarch64 build here [1] > > /usr/bin/ld: .libs/geod: hidden symbol `__aarch64_ldadd4_acq_rel' in > /usr/lib/gcc/aarch64-redhat-linux/10/libgcc.a(ldadd_4_4.o) is referenced by > DSO > /usr/bin/ld: final link failed: bad value > collect2: error: ld returned 1 exit status > > Never seen anything like this, any ideas? #1830472 Jakub ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
[Bug 1829983] perl-HTML-Form for EL8
https://bugzilla.redhat.com/show_bug.cgi?id=1829983 Fedora Update System changed: What|Removed |Added Status|ASSIGNED|MODIFIED --- Comment #3 from Fedora Update System --- FEDORA-EPEL-2020-ac3ddf20d3 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-ac3ddf20d3 -- 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
Fedora-Cloud-32-20200502.0 compose check report
No missing expected images. Soft failed openQA tests: 1/1 (x86_64) (Tests completed, but using a workaround for a known bug) ID: 591295 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/591295 -- 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
Re: Hundreds of aarch64 failures with gcc 10.0.1-0.13
> Seems like a lot of things just started to fail to build on aarch64. I also get the following only for aarch64: /usr/bin/ld: index.lib.o: in function `IndexBase::clear(void (*)(void*, int))': /builddir/build/BUILD/audacious-4.0.3/src/libaudcore/index.cc:48: undefined reference to `__aarch64_ldadd8_acq_rel' /usr/bin/ld: index.lib.o: in function `IndexBase::insert(int, int)': /builddir/build/BUILD/audacious-4.0.3/src/libaudcore/index.cc:86: undefined reference to `__aarch64_ldadd8_acq_rel' /usr/bin/ld: ringbuf.lib.o: in function `RingBufBase::alloc(int)': /builddir/build/BUILD/audacious-4.0.3/src/libaudcore/ringbuf.cc:60: undefined reference to `__aarch64_ldadd8_acq_rel' /usr/bin/ld: ringbuf.lib.o: in function `RingBufBase::destroy(void (*)(void*, int))': /builddir/build/BUILD/audacious-4.0.3/src/libaudcore/ringbuf.cc:84: undefined reference to `__aarch64_ldadd8_acq_rel' /usr/bin/ld: strpool.lib.o: in function `String::raw_ref(char const*)': /builddir/build/BUILD/audacious-4.0.3/src/libaudcore/strpool.cc:143: undefined reference to `__aarch64_ldadd4_acq_rel' /usr/bin/ld: strpool.lib.o: in function `String::raw_unref(char*)': /builddir/build/BUILD/audacious-4.0.3/src/libaudcore/strpool.cc:160: undefined reference to `__aarch64_ldadd4_acq_rel' /usr/bin/ld: /builddir/build/BUILD/audacious-4.0.3/src/libaudcore/strpool.cc:163: undefined reference to `__aarch64_cas4_acq_rel' /usr/bin/ld: strpool.lib.o: in function `Getter::found(StrNode*)': /builddir/build/BUILD/audacious-4.0.3/src/libaudcore/strpool.cc:98: undefined reference to `__aarch64_ldadd4_acq_rel' /usr/bin/ld: strpool.lib.o: in function `Remover::found(StrNode*)': /builddir/build/BUILD/audacious-4.0.3/src/libaudcore/strpool.cc:109: undefined reference to `__aarch64_cas4_acq_rel' /usr/bin/ld: tinylock.lib.o: in function `tiny_lock(char*)': /builddir/build/BUILD/audacious-4.0.3/src/libaudcore/tinylock.cc:29: undefined reference to `__aarch64_swp1_acq' /usr/bin/ld: tinylock.lib.o: in function `tiny_lock_read(unsigned short*)': /builddir/build/BUILD/audacious-4.0.3/src/libaudcore/tinylock.cc:37: undefined reference to `__aarch64_ldadd2_acq_rel' /usr/bin/ld: /builddir/build/BUILD/audacious-4.0.3/src/libaudcore/tinylock.cc:39: undefined reference to `__aarch64_ldadd2_acq_rel' /usr/bin/ld: tinylock.lib.o: in function `tiny_unlock_read(unsigned short*)': /builddir/build/BUILD/audacious-4.0.3/src/libaudcore/tinylock.cc:46: undefined reference to `__aarch64_ldadd2_acq_rel' /usr/bin/ld: tinylock.lib.o: in function `tiny_lock_write(unsigned short*)': /builddir/build/BUILD/audacious-4.0.3/src/libaudcore/tinylock.cc:52: undefined reference to `__aarch64_cas2_acq_rel' /usr/bin/ld: tinylock.lib.o: in function `tiny_unlock_write(unsigned short*)': /builddir/build/BUILD/audacious-4.0.3/src/libaudcore/tinylock.cc:58: undefined reference to `__aarch64_ldadd2_acq_rel' /usr/bin/ld: tuple.lib.o: in function `TupleData::ref(TupleData*)': /builddir/build/BUILD/audacious-4.0.3/src/libaudcore/tuple.cc:391: undefined reference to `__aarch64_ldadd4_acq_rel' /usr/bin/ld: tuple.lib.o: in function `TupleData::unref(TupleData*)': /builddir/build/BUILD/audacious-4.0.3/src/libaudcore/tuple.cc:398: undefined reference to `__aarch64_ldadd4_acq_rel' /usr/bin/ld: tuple.lib.o: in function `TupleData::copy_on_write(TupleData*)': /builddir/build/BUILD/audacious-4.0.3/src/libaudcore/tuple.cc:407: undefined reference to `__aarch64_ldadd4_acq_rel' /usr/bin/ld: tuple.lib.o: in function `TupleData::unref(TupleData*)': /builddir/build/BUILD/audacious-4.0.3/src/libaudcore/tuple.cc:398: undefined reference to `__aarch64_ldadd4_acq_rel' /usr/bin/ld: /builddir/build/BUILD/audacious-4.0.3/src/libaudcore/tuple.cc:398: undefined reference to `__aarch64_ldadd4_acq_rel' /usr/bin/ld: tuple.lib.o:/builddir/build/BUILD/audacious-4.0.3/src/libaudcore/tuple.cc:391: more undefined references to `__aarch64_ldadd4_acq_rel' follow collect2: error: ld returned 1 exit status Failed to link libaudcore.so! ___ 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
Aarch64 build failure: hidden symbol `__aarch64_ldadd4_acq_rel' in /usr/lib/gcc/aarch64-redhat-linux/10/libgcc.a(ldadd_4_4.o) is referenced by DSO
Hi I'm stuck on the following build failure of the aarch64 build here [1] /usr/bin/ld: .libs/geod: hidden symbol `__aarch64_ldadd4_acq_rel' in /usr/lib/gcc/aarch64-redhat-linux/10/libgcc.a(ldadd_4_4.o) is referenced by DSO /usr/bin/ld: final link failed: bad value collect2: error: ld returned 1 exit status Never seen anything like this, any ideas? Thanks Sandro [1] https://koji.fedoraproject.org/koji/taskinfo?taskID=44027889 ___ 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: Grub, EFI, and SELinux
On Fri, May 1, 2020 at 12:03 PM Jerry James wrote: > > On Fri, May 1, 2020 at 7:55 AM Christopher wrote: > > Can anybody tell me why the grub package seems to want to label files > > on the EFI partition during updates? > > I had thought that, by definition, EFI partitions were basically FAT, > > which doesn't support the extended attributes for SELinux contexts... > > > > So, why does the Grub package insist on attempting to label the EFI > > partition, as in the following? > > > > Upgrading: grub2-common-1:2.04-15.fc32.noarch > >2/127 > > error: lsetfilecon: (/boot/efi/EFI/fedora, > > system_u:object_r:boot_t:s0) Operation not supported > > > > I noticed this first on F31 for the first time, awhile back, but I > > figured it was harmless and would be fixed eventually. However, since > > it has been happening for months on F31, and still is happening on F32 > > now that I've upgraded, I'm wondering if there's a good reason why > > it's trying to do this. > > See: > https://bugzilla.redhat.com/show_bug.cgi?id=1722766 > https://github.com/rpm-software-management/rpm/pull/976 Those are bugs filed against RPM. Is the RPM package responsible for executing lsetfilecon, or is it the grub2 package? If the grub2 package, it seems to me that they should know that EFI partitions will never support lsetfilecon and they should never try. If it's RPM, then it looks like it is suppressed upstream and the fix will be incorporated eventually. I guess I don't know which component is actually responsible for causing the execution of lsetfilecon. ___ 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
Schedule for Monday's FESCo Meeting (2020-05-04)
Following is the list of topics that will be discussed in the FESCo meeting Monday at 15:00UTC in #fedora-meeting-1 on irc.freenode.net. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/UTCHowto or run: date -d '2020-05-04 15:00 UTC' Links to all issues to be discussed can be found at: https://pagure.io/fesco/report/meeting_agenda = Discussed and Voted in the Ticket = F33 Self-Contained Change: Erlang 23 https://pagure.io/fesco/issue/2380 APPROVED (+4, 0, -0) = Followups = #topic #2382 2382 systemd default service exception for rpmdb-rebuild service https://pagure.io/fesco/issue/2382 No FESCo-approved exception is needed in this case. = New business = #topic #2372 F33 Self-contained Change: Network Time Security https://pagure.io/fesco/issue/2372 = Open Floor = For more complete details, please visit each individual issue. The report of the agenda items can be found at https://pagure.io/fesco/report/meeting_agenda If you would like to add something to this agenda, you can reply to this e-mail, file a new issue at https://pagure.io/fesco, e-mail me directly, or bring it up at the end of the meeting, during the open floor topic. Note that added topics may be deferred until the following meeting. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: orphaning bleachbit
Yes On Sat, 2 May 2020 at 01:21, Alessio wrote: > On Tue, 2019-12-31 at 10:09 +0300, Silvia Sánchez wrote: > > > > I'm perfectly fine with Fedora's policy regarding Python2. When > > upstream updates to 3, I'll be happy to comaintain together with > > Alessio. > > For the record, bleachbit 4 supporting python 3 was released a couple > of weeks ago. > > > Ciao, > A. > ___ > 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
Fedora-Cloud-31-20200502.0 compose check report
No missing expected images. Passed openQA tests: 1/1 (x86_64) -- 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
Hundreds of aarch64 failures with gcc 10.0.1-0.13
See https://koschei.fedoraproject.org/affected-by/gcc?epoch1=0=10.0.1=0.12.fc33=0=10.0.1=0.13.fc33=f33 https://koschei.fedoraproject.org/affected-by/cpp?epoch1=0=10.0.1=0.12.fc33=0=10.0.1=0.13.fc33=f33 https://koschei.fedoraproject.org/affected-by/libgcc?epoch1=0=10.0.1=0.12.fc33=0=10.0.1=0.13.fc33=f33 Seems like a lot of things just started to fail to build on aarch64. (I've noticed this because Koshcei picked up Python 3.8.3rc1 around the same time, but packages fail to build even when they don't BR Python.) -- 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
Re: F33 system wide change, java-11-openjdk as system jdk
Sure! TYVM! ___ 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] Fedora EPEL 7 updates-testing report
The following Fedora EPEL 7 Security updates need testing: Age URL 626 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-3c9292b62d condor-8.6.11-1.el7 368 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-c499781e80 python-gnupg-0.4.4-1.el7 366 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-bc0182548b bubblewrap-0.3.3-2.el7 75 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-fa8a2e97c6 python-waitress-1.4.3-1.el7 15 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-19d171a465 python34-3.4.10-5.el7 12 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-e3e05f0ce4 gnuchess-6.2.6-1.el7 9 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-a46aedd742 php-horde-horde-5.2.22-1.el7 9 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-23a94e6d3c pxz-4.999.9-19.beta.20200421git.el7 7 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-324f1b735d chromium-81.0.4044.122-1.el7 7 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-c4860b563d openvpn-2.4.9-1.el7 3 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-320cd2c3b5 java-latest-openjdk-14.0.1.7-2.rolling.el7 1 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-12ba1ceddb wordpress-5.1.5-1.el7 The following builds have been pushed to Fedora EPEL 7 updates-testing fedfind-4.4.2-1.el7 ipmctl-02.00.00.3764-1.el7 Details about builds: fedfind-4.4.2-1.el7 (FEDORA-EPEL-2020-b8c0a84eea) Fedora compose and image finder Update Information: This update provides a new release of fedfind, with a single (but important) bug fix: it fixes `get_current_release(branched=True)`, which broke when the new 'ELN' release was added to Bodhi's database, because it assumes all releases have an integer version, but ELN's version is just "eln". ChangeLog: * Fri May 1 2020 Adam Williamson - 4.4.2-1 - New release 4.4.2: Fix get_current_release for new 'ELN' release ipmctl-02.00.00.3764-1.el7 (FEDORA-EPEL-2020-f76f9b80a9) Utility for managing Intel Optane DC persistent memory modules Update Information: Initial 2.x Release 02.00.00.3764 - Removed ipmctl-monitor - Removed libsafec dependency ChangeLog: * Fri May 1 2020 Juston Li - 02.00.00.3764-1 - Release 02.00.00.3764 * Fri Apr 24 2020 Juston Li - 02.00.00.3759-1 - Inital 2.x Release 02.00.00.3759 - Removed ipmctl-monitor - Removed libsafec dependency ___ 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
Fedora-Cloud-30-20200502.0 compose check report
No missing expected images. Passed openQA tests: 1/1 (x86_64) -- 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
[Bug 1824316] perl-Test-PostgreSQL: please add epel8 branch
https://bugzilla.redhat.com/show_bug.cgi?id=1824316 Fedora Update System changed: What|Removed |Added Status|ON_QA |CLOSED Resolution|--- |ERRATA Last Closed||2020-05-02 06:51:39 --- Comment #4 from Fedora Update System --- FEDORA-EPEL-2020-a6b48c5b16 has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. ___ 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
[EPEL-devel] Fedora EPEL 8 updates-testing report
The following Fedora EPEL 8 Security updates need testing: Age URL 9 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-7f0ce51dbd python-bleach-3.1.4-2.el8 7 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-72116e7775 chromium-81.0.4044.122-1.el8 7 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-b928468862 openvpn-2.4.9-1.el8 3 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-c088d8f143 java-latest-openjdk-14.0.1.7-2.rolling.el8 3 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-e16cde6dc5 suricata-5.0.3-1.el8 The following builds have been pushed to Fedora EPEL 8 updates-testing bashtop-0.8.19-1.el8 ipmctl-02.00.00.3764-1.el8 testdisk-7.1-2.el8 Details about builds: bashtop-0.8.19-1.el8 (FEDORA-EPEL-2020-c7e055d1d8) Linux resource monitor Update Information: bashtop first release ChangeLog: ipmctl-02.00.00.3764-1.el8 (FEDORA-EPEL-2020-a4e2167ebf) Utility for managing Intel Optane DC persistent memory modules Update Information: Initial 2.x Release 02.00.00.3764 - Removed ipmctl-monitor - Removed libsafec dependency ChangeLog: * Fri May 1 2020 Juston Li - 02.00.00.3764-1 - Release 02.00.00.3764 * Mon Apr 27 2020 Juston Li - 02.00.00.3759-2 - Fallback to asciidoc * Fri Apr 24 2020 Juston Li - 02.00.00.3759-1 - Inital 2.x Release 02.00.00.3759 - Removed ipmctl-monitor - Removed libsafec dependency testdisk-7.1-2.el8 (FEDORA-EPEL-2020-f724102927) Tool to check and undelete partition, PhotoRec recovers lost files Update Information: libewf-devel is currently missing from rhel 8, ignore it ChangeLog: ___ 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
